Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 14 Apr 2015 23:27:59 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12820996.1429051480000.2697.1429054079590@Atlassian.JIRA>
In-Reply-To: <JIRA.12820996.1429051480000@Atlassian.JIRA>
References: <JIRA.12820996.1429051480000@Atlassian.JIRA>
 <JIRA.12820996.1429051480675@arcas>
Subject: [jira] [Commented] (CASSANDRA-9191) Log and count failure to obtain
 requested consistency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-9191:
---------------------------------------------

Pretty much.  Jonathan suggested a histogram which sounds good to me.

> Log and count failure to obtain requested consistency
> -----------------------------------------------------
>
>                 Key: CASSANDRA-9191
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9191
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Matt Stump
>
> Cassandra should have a way to log failed requests due to failure to obtain requested consistency. This should be logged as error or warning by default. Also exposed should be a counter for the benefit of opscenter. 
> Currently the only way to log this is at the client. Often the application and DB teams are separate and it's very difficult to obtain client logs. Also because it's only visible to the client no visibility is given to opscenter making it difficult for the field to track down or isolate systematic or node level errors.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)