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

FlagDescription
-yAssume 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!


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