You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremiah Jordan (JIRA)" <ji...@apache.org> on 2013/09/10 08:40:51 UTC
[jira] [Created] (CASSANDRA-5992) Add a logger.trace call to
Tracing
Jeremiah Jordan created CASSANDRA-5992:
------------------------------------------
Summary: Add a logger.trace call to Tracing
Key: CASSANDRA-5992
URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
A bunch of stuff is now written to Tracing, and there are no logging trace calls any more. If a node is having issues on the read/write path and tracing can't actually save data, there is no way to see through logging what is going on. Would be nice if we made all Tracing messages also go out at logger.trace so that you could enable that to debug stuff.
Being able to change the RF of the system_traces KS might also help here, but there would still be classes of problems that it would be good to have the logging there for.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira