Step 2 - Data Node Installation

Warning! This page documents an old version of Enterprise InfluxDB, which is no longer actively developed. Enterprise InfluxDB v1.3 is the most recent stable version of Enterprise InfluxDB.

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 second essential component of your InfluxEnterprise 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.

Requirements

To get started, you’ll need the license key that you received at InfluxPortal as well as several servers. The steps below set up two data nodes with each data node on its own server.

Please note that there is no requirement to use that number of servers. The data processes can run on the same or different servers. For high availability and redundancy your cluster should have at least two data nodes. See the Clustering Guide for more on cluster architecture.

The data node servers will need to be able to reach portal.influxdata.com on port 80 or 443. If the data nodes cannot reach portal.influxdata.com on port 80 or 443, the configuration section describes how to use a license file.

Note: By default, data and meta nodes communicate with each other on ports 8088, 8089, and 8091. In a clustered setup you’ll want to configure a load balancer to send client traffic to the data nodes on port 8086, the default port for the HTTP API for writing and querying data.

Data Node Setup

Modify the /etc/hosts file

Add your servers’ hostnames and IP addresses to each cluster server’s /etc/hosts file (the hostnames are representative):

<Data_1_IP> enterprise-data-01
<Data_2_IP> enterprise-data-02

Verification steps:

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:

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.

Set up, configure, and start the data servers

On each data server:

1. Download and install the data server package

Ubuntu & Debian (64-bit)

wget https://dl.influxdata.com/enterprise/releases/influxdb-data_1.0.2-c1.0.4_amd64.deb
sudo dpkg -i influxdb-data_1.0.2-c1.0.4_amd64.deb

RedHat & CentOS (64-bit)

wget https://dl.influxdata.com/enterprise/releases/influxdb-data-1.0.2_c1.0.4.x86_64.rpm
sudo yum localinstall influxdb-data-1.0.2_c1.0.4.x86_64.rpm

2. Edit the configuration file

First, in /etc/influxdb/influxdb.conf, uncomment:

  • hostname at the top of the file and set it to the full hostname of the data node
  • the header of the [http] section
  • auth-enabled in the [http] section and set it to true
  • shared-secret in the [http] section and set it to a long pass phrase that will be used to sign tokens for intra-cluster communication. The Enterprise Web console requires this to be consistent across all data nodes.

Second, in /etc/influxdb/influxdb.conf, set:

  • 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

Note: license-key and license-path 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]

registration-enabled = false
registration-server-url = ""
license-key = "<your_license_key>" #✨ mutually exclusive with license-path
license-path = "/path/to/readable/JSON.license.file" #✨ mutually exclusive with license-key

[meta]
dir = "/var/lib/influxdb/meta" # data nodes do require a local meta directory

[...]

[http] #✨
# enabled = true
# bind-address = ":8086"
auth-enabled = true #✨ this is recommended but not required
# log-enabled = true
# write-tracing = false
# pprof-enabled = false
# https-enabled = false
# https-certificate = "/etc/ssl/influxdb.pem"
#  https-private-key = ""
#  max-row-limit = 10000
#  max-connection-limit = 0
shared-secret = "long pass phrase used for signing tokens" #✨
#  realm = "InfluxDB"

3. Start the data node

On sysvinit systems, enter:

service influxdb start

On systemd systems, enter:

sudo systemctl start influxdb

Verification steps:

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

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

Run the add-data command once and only once for each data node you are joining to the cluster.

Verification steps:

Issue the following command on any meta node:

influxd-ctl show

The expected output is:

Data Nodes
==========
ID   TCP Address
4    enterprise-data-01:8088
5    enterprise-data-02:8088    

Meta Nodes
==========
TCP Address
enterprise-meta-01:8091
enterprise-meta-02:8091
enterprise-meta-03:8091

The output should include every data node that was added to the cluster. The first data node added should have ID=N, where N is equal to one plus the number of meta nodes. In a standard three meta node cluster, the first data node should have ID=4 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 the InfluxEnterprise web console.