[mod_cluster-dev] Configuring checking a crashed worker
jean-frederic clere
jfclere at gmail.com
Thu Aug 13 11:13:02 EDT 2009
On 08/13/2009 04:56 PM, Bela Ban wrote:
> But this works in mod_jk doesn't it ?
mod_jk has a static configuration it is not going to remove something
from the configuration.
>
> Besides, when we have *non-clustered* workers, there is no HA singleton
> telling httpd to remove the crashed worker, so httpd has to do it itself.
>
> I mean, why can't httpd simply remove a worker W is the socket
> connection to W is closed (by W crashing) ?
First an entry corresponding shouldn't disturb mod_cluster, see
MODCLUSTER-92 about telling it is broken. Of course it would possible to
remove broken workers after a while, but I think it must be a
switch-able option and the while should be a parameter... Please create
a JIRA.
Cheers
Jean-Frederic
>
>
> jean-frederic clere wrote:
>> On 08/13/2009 02:06 PM, Bela Ban wrote:
>>> *Which properties do I have to set (I guess in mod-cluster-jboss.beans
>>> in HAModClusterConfig) to remove crashed workers from http's tables ?*
>>
>> You can't... The idea is that the cluster logic will do it by removing
>> the node.
>>
>> Cheers
>>
>> Jean-Frederic
>
More information about the mod_cluster-dev
mailing list