Re: [javagroups-users] Conversion from FD to FD_ALL
by Brian Stansberry
Ok, thanks. Based on that my intent is to defer
https://jira.jboss.org/jira/browse/JBAS-6604 until this is sorted. Would
you agree?
Bela Ban wrote:
> Yes, the change from FD to FD_ALL is correct.
>
> 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
>
>
> Brian Stansberry wrote:
>> I have a task to convert JBoss AS's UDP-based stacks from FD to
>> FD_ALL.[1] I want to make sure I understand the configuration correctly
>> such that I can get the same behavior as we have now for the simple case
>> where one node crashes. (I realize FD_ALL can detect multiple failures
>> more quickly, which is good.)
>>
>> The AS currently uses:
>>
>> <FD timeout="6000" max_tries="5" shun="true"/>
>>
>> Would this be fairly similar:
>>
>> <FD_ALL timeout="30000" interval="6000" shun="true"/>
>>
>> In both case it takes 30 secs to suspect a node, in both cases a message
>> is sent every 6 seconds, and in both cases 5 such messages would have to
>> be lost for some reason before a healthy node would be suspected.
>>
>> [1] https://jira.jboss.org/jira/browse/JBAS-6604
>
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
15 years
Re: [jboss-cluster-dev] [Fwd: [JBoss JIRA] Created: (JBAS-6691) Upgrade JGroups to 2.6.9]
by Brian Stansberry
Great; thanks.
Bela Ban wrote:
> OK, I'll have a chat with Vladimir this afternoon. There are 3 issues
> left in 2.6.9 (2 for Vladimir, 1 for me). If Vladimir has already fixed
> his (I think he has), I can fix mine (minor) today and then we should be
> able to release 2.6.9 early next week, or even this week. I'll keep you
> posted
>
> Brian Stansberry wrote:
>> Bela,
>>
>> I just realized I'd gotten confused about when JGRP-928 was fixed --
>> it's not in 2.6.8 but in the as-yet-unreleased 2.6.9. Can we get a
>> 2.6.9 by mid April? The cutoff for component updates for AS 5.1 is
>> April 20.
>>
>> - Brian
>>
>> -------- Original Message --------
>> Subject: [JBoss JIRA] Created: (JBAS-6691) Upgrade JGroups to 2.6.9
>> Date: Fri, 27 Mar 2009 13:20:22 -0400 (EDT)
>> From: Brian Stansberry (JIRA) <jira-events(a)lists.jboss.org>
>> To: brian.stansberry(a)redhat.com
>>
>> Upgrade JGroups to 2.6.9
>> ------------------------
>>
>> Key: JBAS-6691
>> URL: https://jira.jboss.org/jira/browse/JBAS-6691
>> Project: JBoss Application Server
>> Issue Type: Component Upgrade
>> Security Level: Public (Everyone can see)
>> Components: Clustering
>> Reporter: Brian Stansberry
>> Assignee: Brian Stansberry
>> Fix For: JBossAS-5.1.0.CR1
>>
>>
>> In particular we need the JGRP-928 fix.
>>
>
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
15 years
Conversion from FD to FD_ALL
by Brian Stansberry
I have a task to convert JBoss AS's UDP-based stacks from FD to
FD_ALL.[1] I want to make sure I understand the configuration correctly
such that I can get the same behavior as we have now for the simple case
where one node crashes. (I realize FD_ALL can detect multiple failures
more quickly, which is good.)
The AS currently uses:
<FD timeout="6000" max_tries="5" shun="true"/>
Would this be fairly similar:
<FD_ALL timeout="30000" interval="6000" shun="true"/>
In both case it takes 30 secs to suspect a node, in both cases a message
is sent every 6 seconds, and in both cases 5 such messages would have to
be lost for some reason before a healthy node would be suspected.
[1] https://jira.jboss.org/jira/browse/JBAS-6604
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
15 years, 1 month
[Fwd: [JBoss JIRA] Created: (JBAS-6691) Upgrade JGroups to 2.6.9]
by Brian Stansberry
Bela,
I just realized I'd gotten confused about when JGRP-928 was fixed --
it's not in 2.6.8 but in the as-yet-unreleased 2.6.9. Can we get a 2.6.9
by mid April? The cutoff for component updates for AS 5.1 is April 20.
- Brian
-------- Original Message --------
Subject: [JBoss JIRA] Created: (JBAS-6691) Upgrade JGroups to 2.6.9
Date: Fri, 27 Mar 2009 13:20:22 -0400 (EDT)
From: Brian Stansberry (JIRA) <jira-events(a)lists.jboss.org>
To: brian.stansberry(a)redhat.com
Upgrade JGroups to 2.6.9
------------------------
Key: JBAS-6691
URL: https://jira.jboss.org/jira/browse/JBAS-6691
Project: JBoss Application Server
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.1.0.CR1
In particular we need the JGRP-928 fix.
--
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
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
15 years, 1 month
