cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5992) Add a logger.trace call to Tracing
Date Thu, 07 Apr 2016 08:18:25 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229884#comment-15229884
] 

Marcus Eriksson commented on CASSANDRA-5992:
--------------------------------------------

[~RyanMagnusson] seems this fell between chairs, could you rebase on current trunk?

> 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)

Mime
View raw message