Documentation

influxd-ctl kill-copy-shard

The influxd-ctl kill-copy-shard command aborts an in-progress copy-shard operation.

Usage

influxd-ctl kill-copy-shard <src-tcp-address> <dest-tcp-addr> <shard-id>

Arguments

  • src-tcp-address: TCP bind address of the source data node (host:port)
  • dest-tcp-addr: TCP bind address of the destination data node (host:port)
  • shard-id: Shard ID

Flags

See influxd-ctl global flags.

Examples

influxd-ctl kill-copy-shard data-node-02:8088 data-node-03:8088 39

Was this page helpful?

Thank you for your feedback!


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