[jboss-jira] [JBoss JIRA] Updated: (JBAS-6604) Use FD_ALL in UDP stacks
[
https://jira.jboss.org/jira/browse/JBAS-6604?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-6604:
-----------------------------------
Fix Version/s: Backlog
(was: JBossAS-5.1.0.CR1)
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration]
Moving to backlog, pending resolution of JGRP-937. Bela commented on the JGroups user
mail list:
"However, as I've found out on a recent clustering consulting gig, FD_ALL has
some issues with FD.shun="true" on merging. The issue we ran into was a
shunfest, where entire subclusters shunned all nodes in different subclusters. This lead
to the issue where the cluster never re-merged due to excessive shunning going on.
I've created a JIRA issue [1] to look into getting rid of shunning and only deal with
merging. However, this is going to be in 2.9 the earliest, not in the 2.6 branch.
[1] https://jira.jboss.org/jira/browse/JGRP-937 "
Use FD_ALL in UDP stacks
------------------------
Key: JBAS-6604
URL: https://jira.jboss.org/jira/browse/JBAS-6604
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: Backlog
Per Bela, UDP based stacks should use FD_ALL instead of FD. TCP based stacks should
not.
FD_ALL works better in cases where X > 1 nodes fail; with FD it will take X * the
failure timeout to suspect the Xth node. E.g. 3 nodes C, D, E fail, 30 sec failure
timeout, it will be 90 secs before the failure of E is discovered.
--
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