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.

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

Using read_entry for read_entry_from potentially reads stale entries #7

Open
bmalinconico opened this issue Apr 8, 2019 · 0 comments

Comments

@bmalinconico
Copy link

I'm reviewing the code for use in our projects and had a quick question.

Within level2 you are using the private read_entry method. This means that L1 could return stale data which is sent up to read and rails would then discard it and start a write (in the case of using fetch).

We run into a problem where L1 may be stale, but L2 may not (due to a different machine writing it).

As it appears, the current code would cause a recalculation. Was this intentional?

Only downside I see is that by calling read you are going to end up with a lot more notifications flying around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant