https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
--- Comment #4 from KS ---
Planning to optimize cluster config as below, for now : Kindly provide your
comments on the same.
NEW=
===
https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
--- Comment #3 from KS ---
Java version 1.6. Update 45
Cluster setup is in perfectly running state for the past 3 months. Couple of
times, production setup was restarted, for application patch upgrade. But
tomcat settings was not touched up
https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
--- Comment #2 from Filip Hanik ---
faulty member is tcp://10.160.40.12:
is this member not responding to anything?
now there are ways around this, such as configuring replication to be async.
What happens then is that healthy nodes wi
https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
--- Comment #1 from Mark Thomas ---
What Java version (exactly please) was this running on?
Exactly (as precisely as possible - ideally to the second) how long was this
cluster up before it failed?
--
You are receiving this mail because:
https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
KS changed:
What|Removed |Added
CC||krishna.saran...@gmail.com
--
You are receiv
