Pedro Ruivo <email@example.com> updated the status of jira ISPN-4444 to Coding In Progress
Dan Berindei <firstname.lastname@example.org> updated the status of jira ISPN-4444 to Reopened
Pedro Ruivo <email@example.com> updated the status of jira ISPN-5021 to Coding In Progress
I think we should split this bug in two and mark this issue as resolved
this is a tricky one. I'm currently work on it but I think the solution I have in mind will solve it.
The stale value can be read only for a brief period of time.
Since we want rather *eventual* consistency than guarantee up-to-date reads in crash/join/leave/split-brain scenarios, this issue is not critical to JDG.
Any resilience tests had trouble with https://bugzilla.redhat.com/show_bug.cgi?id=1166243 . I need to test this yet further, but it seems that partition handling is behaving as expected, since the cache is allowed to become inconsistent/provide stale data in certain time window.
This BZ is related to reading stale data, not inconsistent result of writes. What BZ would you like me to verify?
Described test setup is possible.