[jira] [Resolved] (CASSANDRA-5601) Raise logging levels for consistency failures

["Brandon Williams (JIRA)" <ji...@apache.org>]

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

Brandon Williams resolved CASSANDRA-5601.
-----------------------------------------

    Resolution: Duplicate

Closing in favor of CASSANDRA-5618, which actually takes the approach I had in mind.
                
> Raise logging levels for consistency failures
> ---------------------------------------------
>
>                 Key: CASSANDRA-5601
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5601
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremiah Jordan
>            Priority: Minor
>
> Received a suggestion that it might be nice to log consistency failures above DEBUG, so they could be tracked in server side logs more easily.  For example:
> https://github.com/apache/cassandra/blob/cassandra-1.1/src/java/org/apache/cassandra/service/DatacenterReadCallback.java#L108
> or
> https://github.com/apache/cassandra/blob/cassandra-1.1/src/java/org/apache/cassandra/service/ReadCallback.java#L232
> Currently to get those messages you have to enable DEBUG for all of ReadCallback, so you get a log message from https://github.com/apache/cassandra/blob/cassandra-1.1/src/java/org/apache/cassandra/service/ReadCallback.java#L79 for every read, which is very spammy.

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