Documentation

InfluxDB Anti-Entropy API

Note: The Anti-Entropy API is available from the meta nodes and is only available when the Anti-Entropy service is enabled in the data node configuration settings. For information on the configuration settings, see Anti-Entropy settings.

Use the Anti-Entropy service in InfluxDB Enterprise to monitor and repair entropy in data nodes and their shards. To access the Anti-Entropy API and work with this service, use influxd-ctl entropy (also available on meta nodes).

The base URL is:

http://localhost:8086/shard-repair

GET /status

Description

Lists shards that are in an inconsistent state and in need of repair.

Parameters

NameLocated inDescriptionRequiredType
localqueryLimits status check to local shards on the data node handling this requestNoboolean

Responses

Headers

Header nameValue
Acceptapplication/json

Status codes

CodeDescriptionType
200Successful operationobject

Examples

cURL request

curl -X GET "http://localhost:8086/shard-repair/status?local=true" -H "accept: application/json"

Request URL

http://localhost:8086/shard-repair/status?local=true

Responses

Example of server response value:

{
  "shards": [
    {
      "id": "1",
      "database": "ae",
      "retention_policy": "autogen",
      "start_time": "-259200000000000",
      "end_time": "345600000000000",
      "expires": "0",
      "status": "diff"
    },
    {
      "id": "3",
      "database": "ae",
      "retention_policy": "autogen",
      "start_time": "62640000000000000",
      "end_time": "63244800000000000",
      "expires": "0",
      "status": "diff"
    }
  ],
  "queued_shards": [
    "3",
    "5",
    "9"
  ],
  "processing_shards": [
    "3",
    "9"
  ]
}

POST /repair

Description

Queues the specified shard for repair of the inconsistent state.

Parameters

NameLocated inDescriptionRequiredType
idqueryID of shard to queue for repairYesinteger

Responses

Headers

Header nameValue
Acceptapplication/json

Status codes

CodeDescription
204Successful operation
400Bad request
500Internal server error

Examples

cURL request

curl -X POST "http://localhost:8086/shard-repair/repair?id=1" -H "accept: application/json"

Request URL

http://localhost:8086/shard-repair/repair?id=1

POST /cancel-repair

Description

Removes the specified shard from the repair queue on nodes.

Parameters

NameLocated inDescriptionRequiredType
idqueryID of shard to remove from repair queueYesinteger
localqueryOnly remove shard from repair queue on node receiving the requestNoboolean

Responses

Headers

Header nameValue
Acceptapplication/json

Status codes

CodeDescription
204Successful operation
400Bad request
500Internal server error

Examples

cURL request

curl -X POST "http://localhost:8086/shard-repair/cancel-repair?id=1&local=false" -H "accept: application/json"

Request URL

http://localhost:8086/shard-repair/cancel-repair?id=1&local=false

Models

ShardStatus

NameTypeRequired
idstringNo
databasestringNo
retention_policystringNo
start_timestringNo
end_timestringNo
expiresstringNo
statusstringNo

Examples

{
  "shards": [
    {
      "id": "1",
      "database": "ae",
      "retention_policy": "autogen",
      "start_time": "-259200000000000",
      "end_time": "345600000000000",
      "expires": "0",
      "status": "diff"
    },
    {
      "id": "3",
      "database": "ae",
      "retention_policy": "autogen",
      "start_time": "62640000000000000",
      "end_time": "63244800000000000",
      "expires": "0",
      "status": "diff"
    }
  ],
  "queued_shards": [
    "3",
    "5",
    "9"
  ],
  "processing_shards": [
    "3",
    "9"
  ]
}

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