cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Svihla (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9191) Log and count failure to obtain requested consistency
Date Tue, 14 Apr 2015 23:25:59 GMT

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

Ryan Svihla edited comment on CASSANDRA-9191 at 4/14/15 11:25 PM:
------------------------------------------------------------------

JMX counter at least maybe (or is that what you mean by 'expose' ?


was (Author: rssvihla):
JMX counter maybe?

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

Mime
View raw message