Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Eventual Consistency #166

Open
CJStadler opened this issue Mar 14, 2018 · 1 comment
Open

Eventual Consistency #166

CJStadler opened this issue Mar 14, 2018 · 1 comment

Comments

@CJStadler
Copy link

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!
@liath
Copy link
Collaborator

liath commented Mar 21, 2018

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@liath @CJStadler