[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738661#comment-14738661
]
Paulo Motta commented on CASSANDRA-10241:
-----------------------------------------
Updated 2.2+ branch creating debug.log with async appender, and enabling
{{DEBUG}} log on aforementioned packages by default. Cassci test links remain
the same.
I played around with one node, and the verbosity of debug.log seems acceptable,
except for {{org.apache.cassandra.service.GCInspector}} which was logging too
much of these messages:
{noformat}
DEBUG [Service Thread] 2015-09-10 09:07:36,882 ?:? - ParNew GC in 3ms. CMS Old
Gen: 232350496 -> 232350712; Par Eden Space: 41943040 -> 0; Par Survivor Space:
22784 -> 20800
DEBUG [Service Thread] 2015-09-10 09:07:37,026 ?:? - ParNew GC in 4ms. CMS Old
Gen: 232350712 -> 232350840; Par Eden Space: 41943040 -> 0; Par Survivor Space:
20800 -> 22704
DEBUG [Service Thread] 2015-09-10 09:07:37,169 ?:? - ParNew GC in 4ms. CMS Old
Gen: 232350840 -> 232350960; Par Eden Space: 41943040 -> 0; Par Survivor Space:
22704 -> 14528
DEBUG [Service Thread] 2015-09-10 09:07:37,318 ?:? - ParNew GC in 4ms. CMS Old
Gen: 232350960 -> 232351024; Par Eden Space: 41943040 -> 0; Par Survivor Space:
14528 -> 18480
{noformat}
So, took the chance to update {{GCInspector}} and reduce the level of these
logs to {{TRACE}}.
> 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)
