[
https://issues.apache.org/jira/browse/CASSANDRA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662457#comment-14662457
]
Ryan Magnusson edited comment on CASSANDRA-5992 at 8/7/15 9:09 PM:
-------------------------------------------------------------------
adding calls to logger.trace whenever Tracing.trace is called as well as where
tracing is done inside TraceState as well.
was (Author: ryanmagnusson):
add logger.trace whenever Tracing.trace is called.
> Add a logger.trace call to Tracing
> ----------------------------------
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jeremiah Jordan
> Priority: Minor
> Labels: lhf
> Fix For: 2.0.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)
