Replication mode should be a clusterwise value #88
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#88
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While experimenting with garage. I missconfigured one node with replication mode "none", whereas every other node was at 3. This caused some strange behaviors.
I don't think it makes sense to have different nodes with different replication mode, so having nodes with different configuration should error when starting, ignore local value and take the value from the cluster, or at the very least print a warning
Tagging this as a bug because I don't think we can expect normal users to spend 1h in gdb to figure this out.