[jboss-jira] [JBoss JIRA] (JGRP-1856) FD_ALL should not update all mbrs timestamp in handleViewChange

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1856:
--------------------------------

A,B,C,D are all added to {{suspected_mbrs}} and the coordinator will remove them regardless of their timestamps. So I'm not sure I understand what you mean. Can you decribe this in more detail ?

> FD_ALL should not update all mbrs timestamp in handleViewChange
> ---------------------------------------------------------------
>
>                 Key: JGRP-1856
>                 URL: https://issues.jboss.org/browse/JGRP-1856
>             Project: JGroups
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.4.4
>            Reporter: Takayoshi Kimura
>            Assignee: Bela Ban
>
> In large cluster, when multiple instances (e.g. A, B, C, D) gone at once, FD_ALL interval based checker detects first few instances already timed out (e.g. A, B), suspects them and the coord sends a view change.
> In FD_ALL.handleViewChange(), it updates all mbrs timestamps including the rest of dead members (e.g. C, D) and they get extra life until suspect.
> It would be better not to do this so we can expel them sooner.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)