Stop the running rebalanceAdded in 8.10

DELETE 
/cluster/v2/rebalance

Strongly Consistent About endpoint data consistency

Asks the running rebalance to stop once the transfer in flight has finished. Partitions already transferred keep their new leaders, and those the rebalance had not yet reached keep their current ones.

Cancellation requests are idempotent and always accepted. The wasRunning response field can be used to distinguish a cancellation that found a running rebalance from one that did not.

Requires the cluster-admin security chain. Although this operation lists bearerAuth / basicAuth like the rest of the Orchestration Cluster API, it does not accept an Orchestration Cluster user's credentials — only the separate cluster-admin credentials are valid here.

Required permissions

Even when authorization is enabled, this endpoint requires no specific permission. See resources and permissions to learn more.

Responses

200

The cancellation was accepted.

401

The request lacks valid authentication credentials.

Response Headers

WWW-Authenticate

500

An internal error occurred while processing the request.

502

The coordinator was reached, but its response was absent or unusable.

503

No coordinator is currently available or reachable.

504

The coordinator did not answer before the request timeout.