mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2025-01-06 06:20:42 +00:00
Update README note on eventual consistency
AWS promise read-after-write consistency now, but presumably non-AWS S3-compatible services are still eventually consistent.
This commit is contained in:
parent
462b37b0bb
commit
ef3d4e506d
@ -147,7 +147,7 @@ Generally S3 cannot offer the same performance or semantics as a local file syst
|
||||
|
||||
* random writes or appends to files require rewriting the entire object, optimized with multi-part upload copy
|
||||
* metadata operations such as listing directories have poor performance due to network latency
|
||||
* [eventual consistency](https://en.wikipedia.org/wiki/Eventual_consistency) can temporarily yield stale data([Amazon S3 Data Consistency Model](https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel))
|
||||
* non-AWS providers may have [eventual consistency](https://en.wikipedia.org/wiki/Eventual_consistency) so reads can temporarily yield stale data (AWS offers read-after-write consistency [since Dec 2020](https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-now-delivers-strong-read-after-write-consistency-automatically-for-all-applications/))
|
||||
* no atomic renames of files or directories
|
||||
* no coordination between multiple clients mounting the same bucket
|
||||
* no hard links
|
||||
|
Loading…
Reference in New Issue
Block a user