cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10241) Keep a separate production debug log for troubleshooting
Date Thu, 10 Sep 2015 15:54:46 GMT

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

Ariel Weisberg commented on CASSANDRA-10241:
--------------------------------------------

bq. you're a power user, and diagnosing a bug/problem with your cluster.
If you depend on C* you are going to have to work through bugs/problems in your cluster whether
you are a power user or not. I would be surprised that dealing with logs isn't something that
impacts everyone.

Your point on the verbosity of the log today argues for having a way to separate informational
content from debug/trace content. Present a high level easy to read story in the system.log,
and a higher detail version of that story in a different log.

Is there anyone who actually operates Cassandra in production that has an opinion? Especially
on the state of logging today?

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

Mime
View raw message