-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: decommissioning with replication factor one causes outage #27025
Copy link
Copy link
Closed
Labels
A-kv-distributionRelating to rebalancing and leasing.Relating to rebalancing and leasing.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-2-temp-unavailabilityTemp crashes or other availability problems. Can be worked around or resolved by restarting.Temp crashes or other availability problems. Can be worked around or resolved by restarting.
Milestone
Description
Is this a question, feature request, or bug report?
BUG REPORT
Feature request to disallow dropping replication factor to 1 in multi-node cluster is here: #27026
Logs to be provided. Reported by user leonardo on the forum: https://forum.cockroachlabs.com/t/node-decommissioned-but-2-ranges-are-broken-unavailable/1786
- Please describe the issue you observed:
-
What did you do?
In a 6 node cluster, reduced replication factor to 1 and decommissioned node. Node reported decommissioning complete, but two ranges are still leased to the node. -
What did you expect to see?
No ranges leased to node, stopping the node has no impact on data availability. -
What did you see instead?
Stopping the node results in unavailable ranges.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-distributionRelating to rebalancing and leasing.Relating to rebalancing and leasing.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-2-temp-unavailabilityTemp crashes or other availability problems. Can be worked around or resolved by restarting.Temp crashes or other availability problems. Can be worked around or resolved by restarting.