[jboss-jira] [JBoss JIRA] Resolved: (JGRP-759) FLUSH: GMS potential problem

[Vladimir Blagojevic (JIRA)]

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

Vladimir Blagojevic resolved JGRP-759.
--------------------------------------

    Resolution: Done

Resolved on 2.6 branch:

1.82.2.5  +10 -1     JGroups/src/org/jgroups/protocols/pbcast/CoordGmsImpl.java
1.82.2.15 +22 -20    JGroups/src/org/jgroups/protocols/pbcast/FLUSH.java
1.158.2.18 +127 -24   JGroups/src/org/jgroups/JChannel.java


Resolved on HEAD (2.7)

1.189 +129 -26   JGroups/src/org/jgroups/JChannel.java
1.90 +10 -1     JGroups/src/org/jgroups/protocols/pbcast/CoordGmsImpl.java
1.104 +22 -20    JGroups/src/org/jgroups/protocols/pbcast/FLUSH.java

> FLUSH: GMS potential problem
> ----------------------------
>
>                 Key: JGRP-759
>                 URL: http://jira.jboss.com/jira/browse/JGRP-759
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6.3, 2.7
>
>
> [Michael Newcomb]
> When joining with state transfer, the coordinator starts the flush, but
> the joining member stops it. This might lead to an issue because as soon
> as the coordinator casts the new view to everyone (and receives their
> acks) he starts processing the next request in the queue without waiting
> for the flush to be completed.
> I noticed this because I got a 'retrying flush' without ever seeing "...
> Running FLUSH...". So, flushInProgress is still true. The problem might
> arise in that when it retries it sets force=true and that could possibly
> cause a flush to start before the stop has been received.
> Not sure it is an issue, but just thought I'd bring it up.

-- 
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