cassandra-commits mailing list archives

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

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

Paulo Motta edited comment on CASSANDRA-10241 at 9/10/15 2:29 PM:
------------------------------------------------------------------

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

as per CASSANDRA-9376, apparently the use of {{AsyncAppender}} mitigates a significant part
of this overhead

bq. I'd be inclined to introduce a specific low overhead (and very simple) framework for this.

\+1, but I think we can rely on this approach for the time being, and based on user output
we can either turn {{debug.log}} into {{system.log}} (if there isn't much perceived difference
between them) or implement this low overhead logging framework when we see an opportunity
where we want to be even chattier than INFO++.


was (Author: pauloricardomg):
bq. 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).

as per CASSANDRA-9376, apparently the use of {{AsyncAppender}} mitigates a significant part
of this overhead

bq. I'd be inclined to introduce a specific low overhead (and very simple) framework for this.

 +1, but I think we can rely on this approach for the time being, and based on user output
we can either turn {{debug.log}} into {{system.log}} (if there isn't much perceived difference
between them) or implement this low overhead logging framework when we see an opportunity
where we want to be even chattier than INFO+++.

> 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