[infinispan-issues] [JBoss JIRA] (ISPN-6921) Use intersection of expected members and stable topology during merge
Radim Vansa (JIRA)
issues at jboss.org
Tue Aug 2 11:41:01 EDT 2016
[ https://issues.jboss.org/browse/ISPN-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radim Vansa updated ISPN-6921:
------------------------------
Description:
During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B)
There was topology update with BCD in CH, but stable topology is still ABCD.
When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode. Therefore, the ACD does not become available though it has enough data from the stable topology.
was:
During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B)
There was topology update with BCD in CH, but stable topology is still ABCD.
When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode.
> Use intersection of expected members and stable topology during merge
> ---------------------------------------------------------------------
>
> Key: ISPN-6921
> URL: https://issues.jboss.org/browse/ISPN-6921
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha3
> Reporter: Radim Vansa
> Assignee: Dan Berindei
>
> During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B)
> There was topology update with BCD in CH, but stable topology is still ABCD.
> When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode. Therefore, the ACD does not become available though it has enough data from the stable topology.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the infinispan-issues
mailing list