-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: implement allocator support for evaluating decommission viability #91570
Copy link
Copy link
Closed
Labels
A-kv-decom-rolling-restartDecommission and Rolling RestartsDecommission and Rolling RestartsA-kv-distributionRelating to rebalancing and leasing.Relating to rebalancing and leasing.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-kvKV TeamKV Team
Description
As part of #90752, we need to add support to the allocator to be able to evaluate the viability of node decommission, by validating that we have valid upreplication targets for all replicas on the node we intend to decommission. In order to do this, we need to add allocator support for determining actions and allocation targets with states not currently represented in the StorePool.
Part of #91570.
Jira issue: CRDB-21321
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-decom-rolling-restartDecommission and Rolling RestartsDecommission and Rolling RestartsA-kv-distributionRelating to rebalancing and leasing.Relating to rebalancing and leasing.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-kvKV TeamKV Team