Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 9 Sep 2015 22:33:46 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12861111.1441139556000.295646.1441838026131@Atlassian.JIRA>
In-Reply-To: <JIRA.12861111.1441139556000@Atlassian.JIRA>
References: <JIRA.12861111.1441139556000@Atlassian.JIRA>
 <JIRA.12861111.1441139556722@arcas>
Subject: [jira] [Commented] (CASSANDRA-10241) Keep a separate production
 debug log for troubleshooting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-10241:
--------------------------------------------

bq. I just didn't feel comfortable of enabling DEBUG logging by default

But the only difference between #3 here and your original patch is that #3 includes the info level and above, right?  Or is there more to it than that?

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