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: the meta nodes.

To install InfluxDB Enterprise meta nodes, do the following:

  1. Review meta node setup and requirements
  2. Set up meta nodes:
    1. Add DNS entries
    2. Set up, configure, and start the meta services
    3. Join meta nodes to the cluster

Meta node setup and requirements

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.

Note: 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 the Clustering in InfluxDB Enterprise for more on cluster architecture.

Other requirements

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 on port 80 or 443.


Meta nodes communicate over ports 8088, 8089, and 8091.

For licensing purposes, meta nodes must also be able to reach on port 80 or 443. If the meta nodes cannot reach on port 80 or 443, you’ll need to set the license-path setting instead of the license-key setting in the meta node configuration file.

User account

The installation package creates an influxdb user on the operating system. The influxdb user runs the InfluxDB meta service. The 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

  1. Add DNS entries
  2. Set up, configure, and start the meta services
  3. 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).

Record TypeHostnameIP<Meta_1_IP><Meta_2_IP><Meta_3_IP>

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:

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.

I. Download and install the meta service

Ubuntu & Debian (64-bit)
sudo dpkg -i influxdb-meta_1.10.0-c1.10.0_amd64.deb
RedHat & CentOS (64-bit)
sudo yum localinstall influxdb-meta-1.10.0_c1.10.0.x86_64.rpm

For added security, follow these steps to verify the signature of your InfluxDB download with gpg.

  1. Download and import InfluxData’s public key:

    curl -s | gpg --import
  2. Download the signature file for the release by adding .asc to the download URL. For example:

  3. Verify the signature with gpg --verify:

    gpg --verify influxdb-meta-1.10.0_c1.10.0.x86_64.rpm.asc influxdb-meta-1.10.0_c1.10.0.x86_64.rpm

    The output from this command should include the following:

    gpg: Good signature from "InfluxDB Packaging Service <>" [unknown]

II. Edit the configuration file

In /etc/influxdb/influxdb-meta.conf:

  • Uncomment hostname and set to the full hostname of the meta node.
  • Uncomment internal-shared-secret in the [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-secret settings in the configuration files of your data nodes.
  • 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.

The license-key and license-path settings are mutually exclusive and one must remain set to the empty string.

# Hostname advertised by this host for remote addresses.  This must be resolvable by all
# other nodes in the cluster

  # 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

III. Start the meta service

On sysvinit systems, enter:

service influxdb-meta start

On systemd systems, enter:

sudo systemctl start influxdb-meta

Verify meta node process

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 flag when starting the single meta node. Please note that a cluster with only one meta node is not recommended for production environments.

Join meta nodes to the cluster

From one and only one meta node, join all meta nodes including itself. In our example, from enterprise-meta-01, run:

influxd-ctl add-meta enterprise-meta-01:8091
influxd-ctl add-meta enterprise-meta-02:8091
influxd-ctl add-meta enterprise-meta-03:8091

Note: Please 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.

The expected output is:

Added meta node x at enterprise-meta-0x:8091

Verify cluster

To verify the cluster, run the following command on any meta node:

influxd-ctl show

The expected output is:

Data Nodes
ID      TCP Address      Version

Meta Nodes
TCP Address               Version
enterprise-meta-01:8091   1.10.0-c1.10.0
enterprise-meta-02:8091   1.10.0-c1.10.0
enterprise-meta-03:8091   1.10.0-c1.10.0

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!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.