octoleo/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2025-01-07 15:34:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README note on eventual consistency

Browse Source 
AWS promise read-after-write consistency now, but presumably non-AWS S3-compatible services are still eventually consistent.
This commit is contained in:
Adam Johnson 2020-12-14 22:46:12 +00:00 committed by Andrew Gaul
parent 462b37b0bb
commit ef3d4e506d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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 * 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 * 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 atomic renames of files or directories
* no coordination between multiple clients mounting the same bucket * no coordination between multiple clients mounting the same bucket
* no hard links * no hard links