[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738741#comment-14738741
]
Benedict commented on CASSANDRA-10241:
--------------------------------------
Do we really want to use something as heavy weight as our logging frameworks
for this? I like the idea, but the costs of string and log message formatting
aren't small, and certainly our current debug logging level has a noticeably
negative impact on performance, if turned on (this was the case when I first
joined 2 years ago and was doing some analysis). If we're just looking for
something that's INFO++, I don't see why we can't drop that into the regular
system logs at the current INFO level. They're rarely read by anyone but power
users anyway.
I'd be inclined to introduce a specific low overhead (and very simple)
framework for this. This could also permit us to be even chattier, and
(eventually) do some nifty things, like only persisting a sequence of log
messages if something interesting/unexpected happens, or probabilistically, or
if exceptions are being encountered elsewhere on the system, etc.
Of course, it's a bit close to 3.0 to consider something like that, but
personally I'm unlikely to be chattier with this proposal.
> 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)
