[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739140#comment-14739140
]
Jonathan Ellis commented on CASSANDRA-10241:
--------------------------------------------
I'd like to emphasize that we're not talking about turning debug or trace on
for client-generated request paths. There's way too much data generated and
it's unlikely to be useful.
What we're proposing is enabling debug logging ONLY for cluster state changes
like gossip and schema, and infrequent activities like repair. These are
categories that we've historically had trouble tracking down bugs in, so if we
give operators on-by-default debug logging there, the chances that they have
something useful to attach to a bug report goes up immensely.
> Keep a separate production debug log for troubleshooting
> --------------------------------------------------------
>
> Key: CASSANDRA-10241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10241
> Project: Cassandra
> Issue Type: New Feature
> Components: Config
> Reporter: Jonathan Ellis
> Assignee: Paulo Motta
> Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> [~aweisberg] had the suggestion to keep a separate debug log for aid in
> troubleshooting, not intended for regular human consumption but where we can
> log things that might help if something goes wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
