InfluxEnterprise offers highly scalable clusters on your infrastructure and a management UI for working with clusters. The next steps will get you up and running with the first essential component of your InfluxEnterprise cluster: the meta nodes.
You must add 3 meta nodes at minimum while setting up the cluster.
There is no requirement to use exactly that number of servers, but for high availability and redundancy your cluster should have at least three meta nodes and an odd number of meta nodes. More than three meta nodes is not recommended unless the servers are unreliable. See the Clustering Guide for more on cluster architecture.
Note: By default, data and meta nodes communicate with each other on ports
Meta Node Setup
Modify the /etc/hosts file
Add your servers’ hostnames and IP addresses to each cluster server’s
file (the hostnames are representative):
<Meta_1_IP> enterprise-meta-01 <Meta_2_IP> enterprise-meta-02 <Meta_3_IP> enterprise-meta-03
Before proceeding with the installation, verify on each server that the other servers are resolvable. Here is an example set of shell commands using
ping -qc 1 enterprise-meta-01 ping -qc 1 enterprise-meta-02 ping -qc 1 enterprise-meta-03
If there are any connectivity issues resolve them before proceeding with the installation. A healthy cluster requires that every meta node can communicate with every other meta node.
Set up, configure, and start the meta servers
On all three meta servers:
1. Download and install the meta server package
Ubuntu & Debian (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.0.2-c1.0.4_amd64.deb sudo dpkg -i influxdb-meta_1.0.2-c1.0.4_amd64.deb
RedHat & CentOS (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.0.2_c1.0.4.x86_64.rpm sudo yum localinstall influxdb-meta-1.0.2_c1.0.4.x86_64.rpm
2. Edit the configuration file
hostnameto the full hostname of the meta node
[enterprise]section to the full URL of the server that will run the InfluxEnterprise web console. You must fully specify the protocol, IP or hostname, and port. Entering the IP or hostname alone will lead to errors.
[enterprise]section to the license key you received on InfluxPortal, OR
[enterprise]section to the local path to the JSON license file you received from InfluxData
license-pathare mutually exclusive and one must remain set to the empty string.
reporting-disabled = false bind-address = "" hostname = "<enterprise-meta-0x>" #✨ [enterprise] registration-enabled = true #✨ registration-server-url = "http://<web-console-server-IP>:3000" #✨ license-key = "<your_license_key>" #✨ mutually exclusive with license-path license-path = "/path/to/readable/JSON.license.file" #✨ mutually exclusive with license-key
3. Start the meta node
On sysvinit systems, enter:
service influxdb-meta start
On systemd systems, enter:
sudo systemctl start influxdb-meta
Check to see that the process is running by entering:
ps aux | grep -v grep | grep influxdb-meta
You should see output similar to:
influxdb 3207 0.8 4.4 483000 22168 ? Ssl 17:05 0:08 /usr/bin/influxd-meta -config /etc/influxdb/influxdb-meta.conf
Note: It is possible to start the cluster with a single meta node but you must pass the
-single-server flagwhen starting the single meta node. Please note that a cluster with only one meta node is not recommended for production environments.
Join the meta nodes to the cluster
From one and only one meta node, join all meta nodes including itself.
In our example, from
influxd-ctl join enterprise-meta-01:8091 influxd-ctl join enterprise-meta-02:8091 influxd-ctl join enterprise-meta-03:8091
Note: Please make sure that you specify the hostname and port of the meta node during the join process. Please do not specify
localhostas this can cause cluster connection issues.
The expected output is:
Added meta node x at enterprise-meta-0x:8091
Issue the following command on any meta node:
The expected output is:
Meta Nodes ========== TCP Address enterprise-meta-01:8091 enterprise-meta-02:8091 enterprise-meta-03:8091
Note that your cluster must have at least three meta nodes. If you do not see your meta nodes in the output, please retry adding them to the cluster.
Once your meta nodes are part of your cluster move on to the next steps to set up your data nodes. Please do not continue to the next steps if your meta nodes are not part of the cluster.