Documentation

InfluxDB Enterprise

influxd-ctl remove-data

The influxd-ctl remove-data command removes a data node from an InfluxDB Enterprise cluster.

This command is destructive

influxd-ctl remove-data erases all data in the specified data node. Only use this command if you want to permanently remove a data node from your InfluxDB Enterprise cluster.

This command doesn’t delete metadata related to the removed data node from other nodes in the cluster. To remove all metadata about the removed data node, use influxd-ctl leave.

Usage

influxd-ctl remove-data [flags] <data-bind-address>

Arguments

  • data-bind-address: TCP bind address of the data node to remove (host:port)

Flags

FlagDescription
-forceForce the removal of a data node (useful if the node is unresponsive)

Also see influxd-ctl global flags.

Examples

influxd-ctl remove-data data-node-03:8088

Was this page helpful?

Thank you for your feedback!

© 2025 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

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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