-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: decommissioning with replication factor one causes outage #27026
Copy link
Copy link
Closed
Labels
A-kv-clientRelating to the KV client and the KV interface.Relating to the KV client and the KV interface.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)S-0-corruption-or-data-lossUnrecoverable corruption, data loss, or other catastrophic issues that can’t be fixed by upgrading.Unrecoverable corruption, data loss, or other catastrophic issues that can’t be fixed by upgrading.
Description
Is this a question, feature request, or bug report?
FEATURE REQUEST
In multi-node clusters, it's still possible to set replication factor to 1. This can lead to unexpected results, and makes it impossible to survive failure. See #27025 as an example.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-clientRelating to the KV client and the KV interface.Relating to the KV client and the KV interface.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)S-0-corruption-or-data-lossUnrecoverable corruption, data loss, or other catastrophic issues that can’t be fixed by upgrading.Unrecoverable corruption, data loss, or other catastrophic issues that can’t be fixed by upgrading.