Reduce FullTableReplication Write Quorum? #821
Labels
No labels
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#821
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Currently, the FullTableReplication is configured as follow:
We don't have the nice property of R+W > N that is required to have these "read your write" property where, independently of the node you query, you always get the value you previously wrote. So we are eventually consistent in the end.
Knowing that, my proposition is to further reduce W from N-1 to N/2+1. Reducing the number of write will allow users to create bucket, rename them, delete them, and manage their keys, even in the presence of a failure.
This issue is motivated by recent events on Deuxfleurs production deployment, where one of our geographical zone was not available for an extended period of time, and it prevented our users from publishing their websites.
A commit has already been written here:
6558c15863
And it is currently deployed on Deuxfleurs production servers as a hotfix: could we consider upstreaming the change?
I'm fine with changing the write quorum to N/2+1, should we merge your commit in the main branch?
If you trust it, sure!