Documentation

influxd-ctl leave

The influxd-ctl leave command removes a meta or data node from an InfluxDB Enterprise cluster. The command searches for influxd and influxd-meta processes running on the local machine bound to specific ports and determines if that process is an InfluxDB meta or data node.

  • 8088: Data node
  • 8091: Meta node

If the InfluxDB data or meta processes are running on non-default ports, the leave operation cannot detect them.

This command is destructive

influxd-ctl leave erases all metastore information from meta nodes and all data from data nodes. Only use this command if you want to permanently remove a node from your InfluxDB Enterprise cluster.

Usage

influxd-ctl leave [flags]

Flags

Flag Description
-y Assume yes to all prompts

Examples

Remove nodes from a cluster

In the following example, influxd-ctl leave detects the meta node running at cluster-node-03:8091 and the data node running at cluster-node-03:8088 in an existing InfluxDB Enterprise cluster and prompts the user to remove them.

influxd-ctl leave
Command output and interactive prompts
Searching for data node on cluster-node-03:8088...
Remove data node cluster-node-03:8088 from the cluster [y/N]: y
Removed cluster-node-03:8088 from the cluster
Searching for meta node on cluster-node-03:8091...
Remove meta node cluster-node-03:8091 from the cluster [y/N]: y

Successfully left cluster

  * Removed data node cluster-node-03:8088 from cluster
  * Removed meta node cluster-node-03:8091 from cluster

Remove nodes from a cluster and assume yes to all prompts

In the following example, influxd-ctl leave detects the meta node running at cluster-node-03:8091 and the data node running at cluster-node-03:8088 in an existing InfluxDB Enterprise cluster and then, without prompting for input, removes them from the cluster:

influxd-ctl leave -y
Command output
Searching for data node on cluster-node-03:8088...
Removed cluster-node-03:8088 from the cluster
Searching for meta node on cluster-node-03:8091...

Successfully left cluster

  * Removed data node cluster-node-03:8088 from cluster
  * Removed meta node cluster-node-03:8091 from cluster

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: