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

Client near cache order of updates #8652

Closed
ihsandemir opened this issue Aug 2, 2016 · 1 comment
Closed

Client near cache order of updates #8652

ihsandemir opened this issue Aug 2, 2016 · 1 comment

Comments

@ihsandemir
Copy link
Contributor

@ihsandemir ihsandemir commented Aug 2, 2016

Currently the near cache updates does not guarantee the order of events for a certain key. The updates are performed via asynchronous executor runs and it does not guarantee the order of updates. Furthermore, the invalidations via event service is also not ordered.

@sancar sancar added this to the 3.8.1 milestone Feb 14, 2017
@sancar sancar added the Type: Defect label Feb 14, 2017
@sancar
Copy link
Member

@sancar sancar commented Mar 14, 2017

Currently the near cache updates does not guarantee the order of events for a certain key. The updates are performed via asynchronous executor runs and it does not guarantee the order of updates.

This is fixed with latest near cache improvements.

Furthermore, the invalidations via event service is also not ordered.

Keys are ordered in event service with partition id

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

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.