Documentation

influxd-ctl remove-shard

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

This command is destructive

Removing a shard from a data node is a destructive action and cannot be undone.

Usage

influxd-ctl remove-shard <data-bind-address> <shard-id>

Arguments

  • data-bind-address: TCP bind address of the data node to remove the shard from
  • shard-id: Shard ID to remove

Flags

See influxd-ctl global flags.

Examples

influxd-ctl remove-shard data-node-01:8088 31

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