[jboss-jira] [JBoss JIRA] Resolved: (JGRP-622) Stop flush should be invoked by cluster members individually when flush coordinator leaves

Tue Nov 27 08:33:46 EST 2007

     [ http://jira.jboss.com/jira/browse/JGRP-622?page=all ]

Vladimir Blagojevic resolved JGRP-622.
--------------------------------------

    Resolution: Done

Ported relevant files to 2.6 branch.

> Stop flush should be invoked by cluster members individually when flush coordinator leaves
> ------------------------------------------------------------------------------------------
>
>                 Key: JGRP-622
>                 URL: http://jira.jboss.com/jira/browse/JGRP-622
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6.1, 2.7
>
>
> Currently when member A who is a coordinator leaves we execute flush coordinator transfer. That is member A starts flush for view V but member B completes it with stop flush. 
> Member B, neighbor of A, receives a view V where coordinator is excluded, it takes over completion of flush. However, when B sends stop flush, then stop flush might arrive at member C *before* view V sent by A. Thus events get reordered. 
> If each remaining member in V detects (through view) that member A left then each one of the members can complete flush individually by "pretending"  that it received stop flush from A.
> This bug is likely to occur only with bundling disabled. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira