I am running into an issue in the case when something is wrong with several
nodes in the cluster, and the surviving node somehow does not evict the
troublesome nodes and starts accumulating messages.
The current config looks like this:
|
|
|
ok for FD. However is FC appropriate for REPL_ASYNC (the doc suggests it's not
ideal) ?
I think the #1 priority is to detect failure accurately - I am just wondering
what options are left after adding FD if the problem persists.
Last question: is upgrading jgroups to 2.4 (instead of whatever was
We are running into issues with our jbosscache cluster running inside a Tomcat
5.5.17 on JDK1.5.08. We are using the BETA of 1.4.1 that was released back in
november.
Here's the current treecache config and below the current jgroups stack we are
using:
|
|
|
I had a problem recently in production whereby one of the instances in the
cluster failed and had to be terminated (via kill -9).
This is part of a cluster of 4 servers, on which there are 12 cache instances
(1 JVM per server, 3 cache per JVM) in REPL_ASYNC mode.
After a node failure, we restart
I forgot to mention:
* redhat linux
* jdk 1.5.0_08
* tomcat 5.5.17
* jbosscache 1.4.0SP1
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983718#3983718
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983718
__
