Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 29 Jul 2014 20:00:40 +0000 (UTC)
From: "Michael Shuler (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12667747.1378795148226.68587.1406664040121@arcas>
In-Reply-To: <JIRA.12667747.1378795148226@arcas>
References: <JIRA.12667747.1378795148226@arcas>
Subject: [jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to
 Tracing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Shuler updated CASSANDRA-5992:
--------------------------------------

    Fix Version/s: 1.2.19

> 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
>             Fix For: 1.2.19, 2.0.10, 2.1.1
>
>
> 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. Added CASSANDRA-6016 for that.


--
This message was sent by Atlassian JIRA
(v6.2#6252)