[jboss-jira] [JBoss JIRA] (JGRP-1697) Timeout in FLUSH will block all cluster

[Vladimir Blagojevic (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959837#comment-12959837 ] 

Vladimir Blagojevic commented on JGRP-1697:
-------------------------------------------

[~belaban] I have looked into details of this issue and reviewed our design notes - the issue described here is exactly the reason we introduced FLUSH - virtual synchrony. To enable virtual synchrony we need to make sure that all messages from view V1 are delivered to all surviving members in V2. This is definitely not an issue. Recommending reject/close. 
                
> Timeout in FLUSH will block all cluster
> ---------------------------------------
>
>                 Key: JGRP-1697
>                 URL: https://issues.jboss.org/browse/JGRP-1697
>             Project: JGroups
>          Issue Type: Bug
>         Environment: 3.4.0.Alpha2
>            Reporter: shen kim
>            Assignee: Vladimir Blagojevic
>             Fix For: 3.5
>
>
> When I defined FLUSH like this:
> <UDP />
> <PING />
> <MERGE2 />
> <FD_SOCK />
> <FD_ALL />
> <VERIFY_SUSPECT />
> <pbcast.NAKACK2 />
> <UNICAST3 />
> <pbcast.STABLE />
> <pbcast.GMS />
> <UFC />
> <MFC />
> <FRAG2 />
> <pbcast.STATE_TRANSFER />
> <pbcast.FLUSH timeout="0"/>
> If I set timeout to 0, and sending message to all cluster, the all cluster would be block until the new member join cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira