Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 10 Sep 2013 06:40:51 +0000 (UTC)
From: "Jeremiah Jordan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12667747.1378795148226.106528.1378795251560@arcas>
In-Reply-To: <JIRA.12667747.1378795148226@arcas>
References: <JIRA.12667747.1378795148226@arcas>
Subject: [jira] [Created] (CASSANDRA-5992) Add a logger.trace call to
 Tracing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jeremiah Jordan created CASSANDRA-5992:
------------------------------------------

             Summary: Add a logger.trace call to Tracing
                 Key: CASSANDRA-5992
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Jeremiah Jordan
            Priority: Minor


A bunch of stuff is now written to Tracing, and there are no logging trace calls any more.  If a node is having issues on the read/write path and tracing can't actually save data, there is no way to see through logging what is going on.  Would be nice if we made all Tracing messages also go out at logger.trace so that you could enable that to debug stuff.

Being able to change the RF of the system_traces KS might also help here, but there would still be classes of problems that it would be good to have the logging there for.

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