Rebalances a table (reassign instances and segments for a table)
Rebalances a table (reassign instances and segments for a table)
Authorizations
The format of the key is "Basic <token>" or "Bearer <token>"
Path Parameters
Name of the table to rebalance
Query Parameters
OFFLINE|REALTIME
Whether to rebalance table in dry-run mode
Whether to enable pre-checks for table, must be in dry-run mode to enable
Whether to reassign instances before reassigning segments
Whether to reassign CONSUMING segments for real-time table
Whether to rebalance table in bootstrap mode (regardless of minimum segment movement, reassign all segments in a round-robin fashion as if adding new segments to an empty table)
Whether to allow downtime for the rebalance
For no-downtime rebalance, minimum number of replicas to keep alive during rebalance, or maximum number of replicas allowed to be unavailable if value is negative
For no-downtime rebalance, whether to enable low disk mode during rebalance. When enabled, segments will first be offloaded from servers, then added to servers after offload is done while maintaining the min available replicas. It may increase the total time of the rebalance, but can be useful when servers are low on disk space, and we want to scale up the cluster and rebalance the table to more servers.
Whether to use best-efforts to rebalance (not fail the rebalance when the no-downtime contract cannot be achieved)
How often to check if external view converges with ideal states
How long to wait till external view converges with ideal states
How often to make a status update (i.e. heartbeat)
How long to wait for next status update (i.e. heartbeat) before the job is considered failed
Max number of attempts to rebalance
Initial delay to exponentially backoff retry
Whether to update segment target tier as part of the rebalance
Response
successful operation
The response is of type object
.