[jboss-jira] [JBoss JIRA] Resolved: (JGRP-701) Investigate making FD_ALL the default failure detection protocol

Vladimir Blagojevic (JIRA) jira-events at lists.jboss.org
Fri Jul 18 15:19:52 EDT 2008


     [ https://jira.jboss.org/jira/browse/JGRP-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Blagojevic resolved JGRP-701.
--------------------------------------

    Resolution: Done


Ran manual test with FD_ALL - all passed. FD_ALL also passed in combination with FD_SOCK.  

> Investigate making FD_ALL the default failure detection protocol
> ----------------------------------------------------------------
>
>                 Key: JGRP-701
>                 URL: https://jira.jboss.org/jira/browse/JGRP-701
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>            Assignee: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 2.7
>
>
> Replacing FD, so the new combo would be FD_SOCK and FD_ALL. The advantage of FD_ALL is that we detect *many* concurrent failures much faster than FD. 
> E.g if we have A,B,C,D,E and B and C fail, and FD.timeout=1000 and FD.max_tries=3, FD_ALL.timeout=3000 and FD_ALL.interval=1000, then:
> FD will take timeout * max_tries ms to detect the death of B and the same for C, so a total of 6 seconds.
> FD_ALL will take timeout ms to detect both failures, so a total of 3 seconds.
> FD_ALL is also much simpler in its implementation, therefore simpler to verify for correctness

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list