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

Study possible ways to replicate JPA cache (EclipseLink based) betwee master instances #8922

Closed
mshaposhnik opened this issue Feb 27, 2018 · 0 comments
Closed

Study possible ways to replicate JPA cache (EclipseLink based) betwee master instances #8922

mshaposhnik opened this issue Feb 27, 2018 · 0 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@mshaposhnik
Copy link
Contributor

Description

To enable parallel run of several master instances we need to synchonize state of the JPA caches to avoid data inconsistency.

Docs:
[1] https://wiki.eclipse.org/EclipseLink/Examples/JPA/CacheCoordination
[2] http://www.eclipse.org/eclipselink/documentation/2.5/concepts/cache011.htm
@gorkem gorkem mentioned this issue Feb 27, 2018
Closed
19 tasks
@skabashnyuk skabashnyuk mentioned this issue Mar 1, 2018
Closed
12 tasks
This was referenced Mar 2, 2018
Merged
Merged
@skabashnyuk skabashnyuk added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. status/in-progress This issue has been taken by an engineer and is under active development. kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform sprint/current labels Mar 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@skabashnyuk @mshaposhnik