yas3fs icon indicating copy to clipboard operation
yas3fs copied to clipboard

Published 20 hours ago • verified publisher icon danilop

Eventual Consistency

Open CJStadler opened this issue 6 years ago • 1 comments

Does yas3fs do anything to deal with S3 only providing eventual consistency for read-after-write?

For example, say a node receives an SNS notification that a file has changed and so invalidates its cache. If the node then requests the file from S3 the new version of the file is not guaranteed to be returned. If the old version of the file is then cached it will not be invalidated until the file is updated again.

Does yas3fs somehow wait for the new version of the file? Or does this turn out to not be an issue in practice? Or am I misunderstanding something :)?

Thanks for the awesome project!

CJStadler avatar Mar 14 '18 22:03 CJStadler

I don't believe we do, it would probably behoove us to send the new ETag in change alerts and keep a lisr of list of those changes so we can poll headObject until S3 has synchronized.

PRs are welcome :)

liath avatar Mar 21 '18 17:03 liath