[infinispan-issues] [JBoss JIRA] (ISPN-8993) LocalTopologyManager should not install a reset topology before conflict resolution

[Dan Berindei (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei updated ISPN-8993:
-------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/5866


> LocalTopologyManager should not install a reset topology before conflict resolution
> -----------------------------------------------------------------------------------
>
>                 Key: ISPN-8993
>                 URL: https://issues.jboss.org/browse/ISPN-8993
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 9.2.0.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 9.2.1.Final
>
>
> When the coordinator changes, either because the old one left or because there was a merge, the new coordinator first resets any ongoing rebalance, and then starts a rebalance with the new members. But some nodes could see the post-merge rebalance before the post-merge reset, and they need to reset any old data or inbound transfers first. 
> [LocalTopologyManagerImpl|https://github.com/infinispan/infinispan/blob/22a1fc0b2dae9dd9c5fdedc05b2d9daf9d292308/core/src/main/java/org/infinispan/topology/LocalTopologyManagerImpl.java#L418] is responsible for faking that reset topology update, in order to keep StateConsumerImpl simpler. The problem is that LocalTopologyManagerImpl also creates a reset topology update if the new coordinator started conflict resolution, and that topology update clears all the segments not owned by the local node in the preferred topology.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)