Install InfluxDB Enterprise meta nodes
InfluxDB Enterprise offers highly scalable clusters on your infrastructure and a management UI (via Chronograf) for working with clusters. The installation process is designed for users looking to deploy InfluxDB Enterprise in a production environment. The following steps will get you up and running with the first essential component of your InfluxDB Enterprise cluster–meta nodes.
- Meta node setup and requirements
- Set up meta nodes:
Meta node setup and requirements
At least three meta nodes
The installation process sets up three meta nodes, with each meta node running on its own server.
InfluxDB Enterprise clusters require an odd number of at least three meta nodes for high availability and redundancy. We typically recommend three meta nodes. If your servers have chronic communication or reliability issues, you can try adding nodes.
Deploying multiple meta nodes on the same server is strongly discouraged since it creates a larger point of potential failure if that particular server is unresponsive. InfluxData recommends deploying meta nodes on relatively small footprint servers.
See Clustering in InfluxDB Enterprise for more information about 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
Meta nodes communicate over ports
For licensing purposes, meta nodes must also be able to reach
If the meta nodes cannot reach
portal.influxdata.com on port
you’ll need to set the
license-path setting instead of the
setting in the meta node configuration file.
The installation package creates an
influxdb user on the operating system.
influxdb user runs the InfluxDB meta service.
influxdb user also owns certain files needed to start the service.
In some cases, local policies may prevent the local user account from being created and the service fails to start.
Contact your systems administrator for assistance with this requirement.
Set up meta nodes
- Add DNS entries
- Set up, configure, and start the meta services
- Join meta nodes to the cluster
Add DNS entries
Ensure that your servers’ hostnames and IP addresses are added to your network’s DNS environment. The addition of DNS entries and IP assignment is usually site and policy specific. Contact your DNS administrator for assistance as necessary. Ultimately, use entries similar to the following (hostnames and domain IP addresses are representative).
Verify DNS resolution
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
We highly recommend that each server be able to resolve the IP from the hostname alone as shown here. Resolve any connectivity issues 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 services
Perform the following steps on each meta server:
Download and install the meta service
InfluxDB Enterprise 1.11+ provides a standard build and a Federal Information Processing Standards (FIPS)-compliant build. Instructions for both are provided below.
Ubuntu & Debian (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.11.3-c1.11.3-1_amd64.deb sudo dpkg -i influxdb-meta_1.11.3-c1.11.3-1_amd64.deb
wget https://dl.influxdata.com/enterprise/releases/fips/influxdb-meta_1.11.3-c1.11.3-1_amd64.deb sudo dpkg -i influxdb-meta_1.11.3-c1.11.3-1_amd64.deb
RedHat & CentOS (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.11.3_c1.11.3-1.x86_64.rpm sudo yum localinstall influxdb-meta-1.11.3_c1.11.3-1.x86_64.rpm
wget https://dl.influxdata.com/enterprise/releases/fips/influxdb-meta-1.11.3_c1.11.3-1.x86_64.rpm sudo yum localinstall influxdb-meta-1.11.3_c1.11.3-1.x86_64.rpm
Recommended: Verify the authenticity of the release download
For added security, follow these steps to verify the signature of your InfluxDB download with
Download and import InfluxData’s public key:
curl -s https://repos.influxdata.com/influxdata-archive_compat.key | gpg --import
Download the signature file for the release by adding
.ascto the download URL. For example:
Verify the signature with
gpg --verify influxdb-meta-1.11.3_c1.11.3-1.x86_64.rpm.asc influxdb-meta-1.11.3_c1.11.3-1.x86_64.rpm
The output from this command should include the following:
gpg: Good signature from "InfluxDB Packaging Service <firstname.lastname@example.org>" [unknown]
Edit the configuration file
hostnameand set to the full hostname of the meta node.
[meta]section and set it to a long pass phrase to be used in JWT authentication for intra-node communication. This value must the same for all of your meta nodes and match the
[meta] meta-internal-shared-secretsettings in the configuration files of your data nodes.
[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-pathsettings are mutually exclusive and one must remain set to the empty string.
If using a FIPS-compliant InfluxDB Enterprise build, also do the following:
[enterprise].license-pathto the local path to the JSON license file you received from InfluxData.
# Hostname advertised by this host for remote addresses. This must be resolvable by all # other nodes in the cluster hostname="<enterprise-meta-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 # 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] # FIPS-compliant builds do not support bcrypt for password hashing password-hash = "pbkdf2-sha512"
Start the meta service
Optional: Verify the
influxdb-meta service is running
Run the following command to search for a running
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
It is possible to start the cluster with a single meta node but you
must pass the
-single-server flag when starting the single meta node.
Please note that a cluster with only one meta node is not recommended for
Join meta nodes to the cluster
From one and only one meta node, join all meta nodes including itself.
For example, from
influxd-ctl add-meta enterprise-meta-01:8091 influxd-ctl add-meta enterprise-meta-02:8091 influxd-ctl add-meta enterprise-meta-03:8091
Make sure that you specify the fully qualified host name of
the meta node during the join process.
Please do not specify
localhost as this can cause cluster connection issues.
Optional: Verify the meta nodes are added to the cluster
To verify the meta nodes are added to the cluster, run the following command on any meta node:
The expected output is:
Data Nodes ========== ID TCP Address Version Meta Nodes ========== TCP Address Version enterprise-meta-01:8091 1.11.3-c1.11.3 enterprise-meta-02:8091 1.11.3-c1.11.3 enterprise-meta-03:8091 1.11.3-c1.11.3
Note that your cluster must have at least three meta nodes. If you do not see your meta nodes in the output, retry adding them to the cluster.
After your meta nodes are part of your cluster, install data nodes.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.