Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 13 May 2013 22:41:17 +0000 (UTC)
From: "Alex Zarutin (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12636052.1362756348867.312317.1368484877251@arcas>
In-Reply-To: <JIRA.12636052.1362756348867@arcas>
References: <JIRA.12636052.1362756348867@arcas>
Subject: [jira] [Commented] (CASSANDRA-5322) Make dtest logging more
 granular
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Zarutin commented on CASSANDRA-5322:
-----------------------------------------

>From Ryan:

Dtests create and destroy the entire cluster before/after each test, I don't believe we currently have a need to swap testing configurations during the lifetime of a cassandra process, only that we need to control it before it's started.

So, I think you've stated the task appropriately, except I would change "we need to be able to turn on/off logging for the single cassandra class (or multiple cassandra classes) on the  fly" to "we need to be able to turn on/off logging for cassandra classes programattically before cassandra starts"
                
> Make dtest logging more granular 
> ---------------------------------
>
>                 Key: CASSANDRA-5322
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5322
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ryan McGuire
>            Assignee: Alex Zarutin
>
> From Brandon: We need a way (might need to go in ccm, I haven't looked) to just set one class to DEBUG or TRACE, like we'd do in conf/log4-server.properties but with an env var preferably, so I can control it via buildbot, since it's better at reproducing some issues than I am sometimes, but I don't want to run the full hammer debug all the time. Also, a way to set Tester.allow_log_errors to false via an env var, since sometimes there's an error there that takes a while to fix but is cosmetic, and in the meantime I want to catch new failures so we don't fall behind.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira