[jboss-jira] [JBoss JIRA] (JGRP-1509) GMS: low leave_timeout may cause incorrect view installation

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1509:
--------------------------------

Also, if we add a merge protocol (MERGE2 or MERGE3) to tmp.xml, A does get the new view {B,C} after some time.
However, we should not rely on this and find a solution which works regardless of whether a merge protocol is in the config, or leave_timeout is greater than the retransmit interval of NAKACK(2).
                
> GMS: low leave_timeout may cause incorrect view installation
> ------------------------------------------------------------
>
>                 Key: JGRP-1509
>                 URL: https://issues.jboss.org/browse/JGRP-1509
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.0.15, 3.2
>
>         Attachments: tmp.xml
>
>
> - {A}
> - B joins, then C, the view is A2={A,B,C}
> - *No* messages are sent
> - GMS.leave_timeout=100
> - NAKACK2.xmit_interval=1000
> - A leaves gracefully (JChannel.disconnect())
> - A multicasts B3={B,C}, the seqno is #3
> - B discarded A#2 (view {A,B,C}), as it was not yet server
> - B now asks A for retransmission of #2 before it can deliver #3 (the new view)
> (- The retransmission kicks in ca. every 1 sec)
> - However, A is gone, so C will loop asking A to retransmit #3 and will therefore never install view B2 !

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