[ 
https://issues.apache.org/jira/browse/CASSANDRA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeremy Hanna updated CASSANDRA-5992:
------------------------------------
    Complexity: Low Hanging Fruit

> 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: Legacy/Observability
>            Reporter: Jeremiah Jordan
>            Assignee: Ryan Magnusson
>            Priority: Low
>              Labels: lhf
>             Fix For: 4.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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to