Documentation

InfluxDB Enterprise

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!

© 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.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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