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

Vladimir Blagojevic (JIRA) jira-events at lists.jboss.org
Wed May 21 11:52:02 EDT 2008


    [ http://jira.jboss.com/jira/browse/JGRP-759?page=comments#action_12413563 ] 
            
Vladimir Blagojevic commented on JGRP-759:
------------------------------------------

Yes I was aware of this. Flush will retry until it succeeds or it times out in these cases. If users are dealing with particularly long state transfers, say more than 10 seconds, FLUSH retry_timeout parameter can be increased accordingly. 

Suggesting a rejection of this issue.

> 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.7, 2.6.3
>
>
> [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

        



More information about the jboss-jira mailing list