Drop features for dealing with eventually consistent servers?

archiecobbs / s3backer

FUSE/NBD single file backing store via Amazon S3

Other

538 stars 77 forks source link

Closed Nikratio closed 2 years ago

Nikratio commented 2 years ago

Given that AWS S3 now offers immediate consistency for all requests (https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/), would it make sense to drop the s3backer code that deals exclusively with eventual consistency (md5 cache, minWriteDelay, etc)?

I don't expect performance gain, but it may make the code less complex.

archiecobbs commented 2 years ago

Wow! I had not heard this and that's great news.

I think we should keep the ec_protect layer around, because other S3-compatible services may not provide this new guarantee.

But changing the default behavior so that ec_protect is not used (i.e., ----md5CacheSize=0) would make sense.

archiecobbs commented 2 years ago

Done in a757248.