Document the consistency model #289
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#289
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?
After reading the design goals [1] and benchmark [2], I'm curious about the consistency model. It's obvious that you are using a quite weak consistency model to get better performance, but this model is not described in details. I would expect that description to be part of the design goals, it's quite important to know what can be expected from garage.
I did find a bit more details (in French) in these slides [3] but it's still very high-level.
[1] https://garagehq.deuxfleurs.fr/documentation/design/goals/
[2] https://garagehq.deuxfleurs.fr/documentation/design/benchmarks/
[3] https://git.deuxfleurs.fr/Deuxfleurs/garage/src/branch/main/doc/talks/2020-12-02_wide-team/talk.pdf
Garage Consistency Model for the S3 API is the same as Amazon's New Strong-Consistency Model, ie. Read Your Write. You can find more details here: https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html#ConsistencyModel
Considering the admin's API, it has a weaker consistency compared to S3. We plan to define it more precisely soon.