[infinispan-issues] [JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services

[Ryan Emerson (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482135#comment-13482135 ] 

Ryan Emerson commented on ISPN-8400:
------------------------------------

So Caching Service will be REMOVE_ALL like you say.

For Shared Memory Service, I was thinking that we would utilise the PREFERRED_NON_NULL policy. So this means that if an entry exists in the preferred partition (partition coordinating the merge) than we utilise that value, however if this is NULL we utilise the non-null value from the other partition. As we will be preventing read/writes once the split-brain has been detected, the window for conflicts is going to be reasonably small. So I'm not sure we can do much better than this for now. More advanced options might be available when we have versioning, eventual consistency etc.

> 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)