[ https://issues.apache.org/jira/browse/CASSANDRA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-5992: --------------------------------------- Fix Version/s: 3.x > Add a logger.trace call to Tracing > ---------------------------------- > > Key: CASSANDRA-5992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5992 > Project: Cassandra > Issue Type: Improvement > Reporter: Jeremiah Jordan > Priority: Minor > Labels: lhf > Fix For: 3.x > > Attachments: CASSANDRA-5992.txt > > > 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. Added CASSANDRA-6016 for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)