-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: method to check decommission by valid replica replacement availability #91571
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 will need to determine the viability of node decommission by evaluating the possibility of replacing each replica on the decommissioning node with a new replica on a valid, available store. In evaluating each replica that exists on the node(s), we can also gather errors and potential remediation steps so that the decommission may become viable.
Jira issue: CRDB-21322
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