mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #515] S3 eventual consistency #286
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#286
Loading…
Add table
Add a link
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?
Originally created by @dangmocrang on GitHub (Dec 13, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/515
Hello,
As I know amazon s3 now free from eventual consistency. All regions now support read-after-write. This issue is mentioned in S3 FAQ https://aws.amazon.com/s3/faqs/
So maybe document section "Eventual consistency" is no need.
Regards,
Dung
@gaul commented on GitHub (Jan 2, 2017):
This is a bit subtle, although the us-standard region has strengthened its consistency guarantees, but Amazon still exhibits eventual behavior in read-after-overwrite and read-after-write-after-read scenarios:
https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel
I document these guarantees but my data are out of date:
https://github.com/andrewgaul/are-we-consistent-yet
@ggtakec commented on GitHub (Jan 15, 2017):
I added URL link(FAQ) in README.md
Thanks @andrewgaul