admin_rebalance
- admin_rebalance(
options?: Record<string, string>,
callback?: GPUdbCallback,
): Promise<AdminRebalanceResponse>Parameters
Optionaloptions: Record<string, string>Optional parameters.
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<AdminRebalanceResponse>
Promise<Types.AdminRebalanceResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:2187
admin_rebalance_request
- admin_rebalance_request(
request: AdminRebalanceRequest,
callback?: GPUdbCallback,
): Promise<AdminRebalanceResponse>Rebalance the data in the cluster so that all nodes contain an equal number of records approximately and/or rebalance the shards to be equally distributed (as much as possible) across all the ranks.
The database must be offline for this operation, see
admin_offline- If
admin_rebalanceis invoked after a change is made to the cluster, e.g., a host was added or removed, sharded data will be evenly redistributed across the cluster by number of shards per rank while unsharded data will be redistributed across the cluster by data size per rank - If
admin_rebalanceis invoked at some point when unsharded data (a.k.a. randomly-sharded) in the cluster is unevenly distributed over time, sharded data will not move while unsharded data will be redistributed across the cluster by data size per rank
NOTE: Replicated data will not move as a result of this call
This endpoint’s processing time depends on the amount of data in the system, thus the API call may time out if run directly. It is recommended to run this endpoint asynchronously via
create_job.Parameters
- request: AdminRebalanceRequest
Request object containing the parameters for the operation
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<AdminRebalanceResponse>
Promise<Types.AdminRebalanceResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:2146
- If
Rebalance the data in the cluster so that all nodes contain an equal number of records approximately and/or rebalance the shards to be equally distributed (as much as possible) across all the ranks.
The database must be offline for this operation, see
admin_offlineadmin_rebalanceis invoked after a change is made to the cluster, e.g., a host was added or removed, sharded data will be evenly redistributed across the cluster by number of shards per rank while unsharded data will be redistributed across the cluster by data size per rankadmin_rebalanceis invoked at some point when unsharded data (a.k.a. randomly-sharded) in the cluster is unevenly distributed over time, sharded data will not move while unsharded data will be redistributed across the cluster by data size per rankNOTE: Replicated data will not move as a result of this call
This endpoint’s processing time depends on the amount of data in the system, thus the API call may time out if run directly. It is recommended to run this endpoint asynchronously via
create_job.