]
Vladimir Blagojevic resolved JGRP-700.
--------------------------------------
Resolution: Done
Resolved on HEAD (2.7)
Revision Changes Path
1.17 +10 -12 JGroups/tests/junit/org/jgroups/tests/MergeTest.java
1.135 +31 -33 JGroups/src/org/jgroups/protocols/pbcast/GMS.java
1.29 +3 -5 JGroups/src/org/jgroups/protocols/pbcast/GmsImpl.java
FLUSH: flushing should span merge
---------------------------------
Key: JGRP-700
URL:
http://jira.jboss.com/jira/browse/JGRP-700
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assigned To: Vladimir Blagojevic
Fix For: 2.7
When we run flush during a merge (say between {A,B} and {C,D}), then the flush protocol
is run only when installing the new merge view {A,B,C,D} in both subgroups *individually*,
e.g. flush is run for {A,B} and for {C,D}. If the flush in {C,D} completes sooner than the
one in {A,B}, C and D will be able to send messages during {A,B}'s flush phase, thus
violating the properties of flush.
The change should be as follows:
- A merge between the 2 subgroups is detected
- If flush is enabled, run the flush protocol in {A,B} and {C,D}, *before* the new view
V2={A,B,C,D} is installed
- Install V2
- When the view installation is complete, ie. A and C have acked it, only *then* complete
the flush and allow members to resume message sending
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: