[
https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin....
]
Emmanuel Bernard commented on ISPN-8400:
----------------------------------------
[~ryanemerson] with reads/writes not accepted once the split brain is detected, do you
think that prefer non null is in anyway shape or form better than remove all conflicting
entries ?
My concern with prefer non null is that it can resurrect old entries it seems.
Adjust merge policies for JDG Online Services
---------------------------------------------
Key: ISPN-8400
URL:
https://issues.jboss.org/browse/ISPN-8400
Project: Infinispan
Issue Type: Feature Request
Components: Cloud Integrations
Reporter: Sebastian Ćaskawiec
Assignee: Ryan Emerson
Both Shared Memory and Caching Service require custom merge policies.
In Caching Service we need to clear out all conflicted entries upon split brain. Shared
Memory service might be a little bit more tricky and we might want to use some different
strategy (but that needs to be checked out).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)