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

Command Description
add-data Add a data node
add-meta Add a meta node
backup Back up a cluster
copy-shard Copy a shard between data nodes
copy-shard-status Show all active copy shard tasks
entropy Manage entropy in a cluster
join Join a meta or data node
kill-copy-shard Abort an in-progress shard copy
ldap Manage LDAP in a cluster
leave Remove a meta or data node
remove-data Remove a data node
remove-meta Remove a meta node
remove-shard Remove a shard from a data node
restore Restore a backup of a cluster
show Show cluster members
show-shards Shows shards in a cluster
node-labels Manage node labels
token Generates a signed JWT token
truncate-shards Truncate current shards
update-data Update a data node

Global flags

Flag Description
-auth-type Authentication type to use (none default, basic, jwt)
-bind Meta node HTTP bind address (default is localhost:8091)
-bind-tls Use TLS
-config Configuration file path
-k Skip certificate verification (ignored without -bind-tls)
-pwd Password for basic authentication (ignored without -auth-type basic)
-secret JWT shared secret (ignored without -auth-type jwt)
-user Username (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!


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: