cassandra-commits mailing list archives

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

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

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

I'm not against exposing this, but I am against logging it.  Someone is going to get into
a situation where this is happening a lot, the logs are going to dominate the cpu and cause
more timeouts, which means more logging of these "errors."

> 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