Documentation

influxd-ctl CLI

The influxd-ctl CLI provides commands for managing your InfluxDB Enterprise cluster. The influxd-ctl utility is available on all InfluxDB Enterprise meta nodes.

Usage

influxd-ctl [global-flags] <command> [command-flags] [arguments]

Commands

CommandDescription
add-dataAdd a data node
add-metaAdd a meta node
backupBack up a cluster
copy-shardCopy a shard between data nodes
copy-shard-statusShow all active copy shard tasks
entropyManage entropy in a cluster
joinJoin a meta or data node
kill-copy-shardAbort an in-progress shard copy
ldapManage LDAP in a cluster
leaveRemove a meta or data node
remove-dataRemove a data node
remove-metaRemove a meta node
remove-shardRemove a shard from a data node
restoreRestore a backup of a cluster
showShow cluster members
show-shardsShows shards in a cluster
node-labelsManage node labels
tokenGenerates a signed JWT token
truncate-shardsTruncate current shards
update-dataUpdate a data node

Global flags

FlagDescription
-auth-typeAuthentication type to use (none default, basic, jwt)
-bindMeta node HTTP bind address (default is localhost:8091)
-bind-tlsUse TLS
-configConfiguration file path
-kSkip certificate verification (ignored without -bind-tls)
-pwdPassword for basic authentication (ignored without -auth-type basic)
-secretJWT shared secret (ignored without -auth-type jwt)
-userUsername (ignored without -auth-type basic or jwt)

Examples

Bind to a remote meta node

influxd-ctl -bind meta-node-02:8091

Authenticate with JWT

influxd-ctl -auth-type jwt -secret oatclusters

Authenticate with basic authentication

influxd-ctl -auth-type basic -user admin -pwd passw0rd

Troubleshoot influxd-ctl authentication


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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