Ivo Ladage - van Doorn created AMDATUCASSANDRA-181:
------------------------------------------------------
Summary: Hector logs verbose warnings and stacktraces when a node
is down
Key: AMDATUCASSANDRA-181
URL: http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-181
Project: Amdatu Cassandra
Issue Type: Improvement
Components: Cassandra client
Affects Versions: 0.2.2
Reporter: Ivo Ladage - van Doorn
Assignee: Ivo Ladage - van Doorn
Fix For: 0.2.3
Attachments: AMDATUCASSANDRA-181.patch
In case the primary node is down (the node where schema modifications are send
to), a timeout exception occurs internally in Hector. Upon such an exception it
will retry the request, until the host is finally marked as down and withdrawn
from the pool of available hosts. In the meantime, lots of stacktraces and
error messages drop by while this doesn't indicate a real serous issue: when
the first node is stopped in a 3-node cluster (with RF 3 and Quorum R/W) for
maintenance these errors already appear. So in this case they are definitely
verbose.
Unfortunately, this verbose logging takes place in the HConnectionManager of
hector, which can only be changed by patching Hector.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
