5:34 a.m.
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/jira/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:23 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/jira/browse/JGRP-1061?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1061:
--------------------------------
The solution was to *prevent* overlapping flushes in the way the merge algorithm works: in
the case of
A: BAC
B: BC
C: BC
The merge coordinator was B and the participants B and A. The total members were {A,B,C}.
In the first step, all members associated with a coordinator are removed from the total
members:
B: BC and members={A}
In the second step, we create individual members lists for the (non-coord) merge
participants:
A: {A}
In this case, we have
B: {B,C} and A: {A}, so the flushes won't overlap.
Another example:
A: AB
B: AB
C: CD
D: CD
If we get responses from A and D, then the merge participants and associated members are
A: {A,B}
C: {C}
D: {D}
The reason that we didn't flush {C,D} as a sub-partition is that we didn't get a
response from C itself, but from D !
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/jira/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:27 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/jira/browse/JGRP-1061?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1061:
--------------------------------
Added test cases in GMS_MergeTest
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/jira/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 a.m.
New subject: [JBoss JIRA] Resolved: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/jira/browse/JGRP-1061?page=com.atlassian.jira.plug...
]
Bela Ban resolved JGRP-1061.
----------------------------
Resolution: Done
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/jira/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:12 a.m.
New subject: [JBoss JIRA] Reopened: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/browse/JGRP-1061?page=com.atlassian.jira.plugin.sy...
]
Bela Ban reopened JGRP-1061:
----------------------------
Doesn't work for the following case:
A: {A,B}
B: {B}
See GMS_MergeTest.testMergeAsymmetricPartitionsWithFlush2()
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:12 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/browse/JGRP-1061?page=com.atlassian.jira.plugin.sy...
]
Bela Ban updated JGRP-1061:
---------------------------
Fix Version/s: 2.10
(was: 2.8)
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/browse/JGRP-1061?page=com.atlassian.jira.plugin.sy...
]
Bela Ban commented on JGRP-1061:
--------------------------------
Possible solution: remove members from flush set which don't have us in their view,
e.g.
A: ABC
B: BC
C: BC
When A tries to flush ABC, it'll fails as it doesn't get a response from C, so we
do the following:
A: ABC: B doesn't have A in its view, remove B. C oesn't have A in its view:
remove C: target set remaining: {A}
B: C has us in its view: target set remaining {BC}
C: B has us in their view, target set remaining: {BC}
So the finalized flush set is:
A: A
B: BC
C: BC
Second example:
A: AB
B: B
Target set:
A: A
B: B
This simple algorithm should give us non overlapping target flush sets
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:52 a.m.
New subject: [JBoss JIRA] Resolved: (JGRP-1061) FLUSH: asymmetric merge fails
[
https://jira.jboss.org/browse/JGRP-1061?page=com.atlassian.jira.plugin.sy...
]
Bela Ban resolved JGRP-1061.
----------------------------
Resolution: Done
FLUSH: asymmetric merge fails
-----------------------------
Key: JGRP-1061
URL: https://jira.jboss.org/browse/JGRP-1061
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10
A: {B,A,C}
B: {B,C}
C: {B,C}
B and C have the same view, but A has a different (older) view which still includes B and
C
The new merge now determines that the partition coordinators for the merge are B and A.
When FLUSH is enabled, before handling the merge request A tries to flush {A,B,C} and B
tries to flush {B,C}. The latter works, but the former fails as A cannot communicate with
B and C !
SOLUTION: the partition for A needs to be {A} and not {B,A,C}.
Is this possible in all cases, or can we NOT prevent merging of overlapping partitions ?
(Then flush would always fail !)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5300
days inactive
5583
days old
7 comments
1 participants
participants (1)
-
Bela Ban (JIRA)