Rebalance Status
See how many replication tasks are pending or dead-lettered, and why.
| Endpoint | Method | Admin Required |
|---|---|---|
/api/v1/admin/cluster/rebalance/status | GET | Yes |
Returns a snapshot of the internal replication outbox: how many tasks are currently pending, how many have exhausted their retries and dead-lettered, and a breakdown of the pending set by reason.
This is a summary. For the full detail behind a count - which node a stuck task targets, its retry schedule, and its last error - see rebalance tasks.
Response
{
"pendingCount": 3,
"failedCount": 0,
"pendingByReason": {
"write": 1,
"rebalance": 2
},
"replicationFactor": 3
}
Response Fields
pendingCount
integer
Number of tasks currently pending (queued or retrying).
failedCount
integer
Number of tasks that exhausted their retry budget (8 attempts) and were dead-lettered. Retained for 7 days before automatic purge.
pendingByReason
object
Pending task count grouped by why it exists:
write (a synchronous quorum write's straggler catch-up), rebalance (copying an object to a node that gained responsibility for it), or reclaim (removing a stale copy from a node that lost responsibility, only once every new owner is confirmed to have it).replicationFactor
integer
The cluster-wide replication factor (currently fixed at
3, not configurable per bucket).