InfluxDB Enterprise 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 second essential component of your InfluxDB Enterprise cluster: the data nodes.
If you have not set up your meta nodes, please visit Meta Node Installation. Bad things can happen if you complete the following steps without meta nodes.
Data Node Setup Description and Requirements
The Production Installation process sets up two data nodes
and each data node runs on its own server.
You must have a minimum of two data nodes in a cluster.
InfluxDB Enterprise clusters require at least two data nodes for high availability and redundancy.
Note: that there is no requirement for each data node to run on its own server. However, best practices are to deploy each data node on a dedicated server.
See the Clustering Guide for more on cluster architecture.
License key or file
InfluxDB Enterprise requires a license key OR a license file to run.
Your license key is available at InfluxPortal.
Contact support at the email we provided at signup to receive a license file.
License files are required only if the nodes in your cluster cannot reach
portal.influxdata.com on port
Data nodes communicate over ports
For licensing purposes, data nodes must also be able to reach
If the data nodes cannot reach
portal.influxdata.com on port
you’ll need to set the
license-path setting instead of the
setting in the data node configuration file.
InfluxDB Enterprise does not function as a load balancer.
You will need to configure your own load balancer to send client traffic to the
data nodes on port
8086 (the default port for the HTTP API).
Data node setup
Step 1: Modify the
Add your servers’ hostnames and IP addresses to each cluster server’s
file (the hostnames below are representative).
<Data_1_IP> enterprise-data-01 <Data_2_IP> enterprise-data-02
Before proceeding with the installation, verify on each meta and data 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 ping -qc 1 enterprise-data-01 ping -qc 1 enterprise-data-02
If there are any connectivity issues resolve them before proceeding with the installation. A healthy cluster requires that every meta and data node can communicate with every other meta and data node.
Step 2: Set up, Configure, and start the Data Services
Perform the following steps on each data server.
I. Download and Install the Data Service
Ubuntu & Debian (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-data_1.3.8-c1.3.8_amd64.deb sudo dpkg -i influxdb-data_1.3.8-c1.3.8_amd64.deb
RedHat & CentOS (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-data-1.3.8_c1.3.8.x86_64.rpm sudo yum localinstall influxdb-data-1.3.8_c1.3.8.x86_64.rpm
II. Edit the Configuration File
hostnameat the top of the file and set it to the full hostname of the data node
[http]section and set it to
[http]section and set it to a long pass phrase that will be used to sign tokens for intra-cluster communication. This value must be consistent across all data nodes.
license-key in the
[enterprise] section to the license key you received on InfluxPortal OR
license-path in the
[enterprise] section to the local path to the JSON license file you received from InfluxData.
license-pathsettings are mutually exclusive and one must remain set to the empty string.
# Change this option to true to disable reporting. # reporting-disabled = false # bind-address = ":8088" hostname="<enterprise-data-0x>" #✨ [enterprise] # license-key and license-path are mutually exclusive, use only one and leave the other blank license-key = "<your_license_key>" #✨ mutually exclusive with license-path # The path to a valid license file. license-key and license-path are mutually exclusive, # use only one and leave the other blank. license-path = "/path/to/readable/JSON.license.file" #✨ mutually exclusive with license-key [meta] # Where the cluster metadata is stored dir = "/var/lib/influxdb/meta" # data nodes do require a local meta directory [...] [http] # Determines whether HTTP endpoint is enabled. # enabled = true # The bind address used by the HTTP service. # bind-address = ":8086" # Determines whether HTTP authentication is enabled. auth-enabled = true #✨ this is recommended but not required [...] # The JWT auth shared secret to validate requests using JSON web tokens. shared-secret = "long pass phrase used for signing tokens" #✨
III. Start the data service
On sysvinit systems, enter:
service influxdb start
On systemd systems, enter:
sudo systemctl start influxdb
Check to see that the process is running by entering:
ps aux | grep -v grep | grep influxdb
You should see output similar to:
influxdb 2706 0.2 7.0 571008 35376 ? Sl 15:37 0:16 /usr/bin/influxd -config /etc/influxdb/influxdb.conf
If you do not see the expected output, the process is either not launching or is exiting prematurely. Check the logs for error messages and verify the previous setup steps are complete.
If you see the expected output, repeat for the remaining data nodes. Once all data nodes have been installed, configured, and launched, move on to the next section to join the data nodes to the cluster.
Join the data nodes to the cluster
influxd-ctl update-data, skip the rest of this guide.
On one and only one of the meta nodes that you set up in the previous document, run:
influxd-ctl add-data enterprise-data-01:8088 influxd-ctl add-data enterprise-data-02:8088
The expected output is:
Added data node y at enterprise-data-0x:8088
add-data command once and only once for each data node you are joining
to the cluster.
Issue the following command on any meta node:
The expected output is:
Data Nodes ========== ID TCP Address Version 4 enterprise-data-01:8088 1.3.8-c1.3.8 5 enterprise-data-02:8088 1.3.8-c1.3.8 Meta Nodes ========== TCP Address Version enterprise-meta-01:8091 1.3.8-c1.3.8 enterprise-meta-02:8091 1.3.8-c1.3.8 enterprise-meta-03:8091 1.3.8-c1.3.8
The output should include every data node that was added to the cluster.
The first data node added should have
N is equal to one plus the number of meta nodes.
In a standard three meta node cluster, the first data node should have
Subsequently added data nodes should have monotonically increasing IDs.
If not, there may be artifacts of a previous cluster in the metastore.
If you do not see your data nodes in the output, please retry adding them to the cluster.
Once your data nodes are part of your cluster move on to the final step to set up Chronograf.