Documentation

InfluxDB Enterprise

influxd-ctl add-meta

The influxd-ctl add-meta command adds a meta node to an InfluxDB Enterprise cluster.

By default, influxd-ctl adds the specified meta node to the local meta node’s cluster. Use add-meta instead of the join argument when installing a meta node an InfluxDB Enterprise cluster.

Usage

influxd-ctl [flags] add-meta <http-bind-address>

Arguments

  • http-bind-address: HTTP bind address of the meta node to add to the cluster (host:port)

Flags

See influxd-ctl global flags.

Examples

Add a meta node to a cluster

influxd-ctl add-meta cluster-meta-node-03:8091

Add a meta node to a cluster using a remote meta node

influxd-ctl -bind cluster-meta-node-01:8091 add-meta cluster-meta-node-03:8091

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Where are you running InfluxDB?

Customize your InfluxDB Enterprise URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB Enterprise HTTP settings.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2