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:00:47 GMT

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

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

We shouldn't turn debug/trace on for everything. Just for a subset. The goal is to have an
option for logging state that is inappropriate for a human readable log, but not so onerous
that it causes an unacceptable performance impact. 

It's definitely true that we could log much higher volumes if we logged in an efficient binary
encoding and then wrote a formatter (plus other capabilities). That is a bigger time investment
for more functionality. This approach like a relatively simple low risk way to allow logging
more things that could exist alongside a binary logging mechanism.

I think if only power users can read our logs that's kind of a bad thing? I would be really
surprised if there weren't a lot of people depending on the regular log output being human
readable. Seems to me like that shouldn't be the case. Whenever something goes wrong the logs
are the first thing someone has to parse.

If there is a noticeable performance impact then we need to back off on what we are logging.
I think that turning on logging by class or package is not the way to go here. We should do
it at the statement level, possibly by using a logger(s) that will go into this specific log
suitable for production log.

Paulo the GCInspector logs are redundant with the GC logs which are going to be on by default
as part of CASSANDRA-10140. Demoting to trace is fine with me.

> 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