cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9191) Log and count failure to obtain requested consistency
Date Wed, 15 Apr 2015 01:17:59 GMT


Jonathan Ellis commented on CASSANDRA-9191:

It's already logged at debug.

                    if (Tracing.isTracing())
                        Tracing.trace("{}; received {} of {} responses{}",
                                      isTimeout ? "Timed out" : "Failed", responseCount, blockFor,
                    else if (logger.isDebugEnabled())
                        logger.debug("Read {}; received {} of {} responses{}", (isTimeout
? "timeout" : "failure"), responseCount, blockFor, gotData);

And yes, debug gives you way too much stuff, but that's exactly the problem Brandon called
out.  There's no way around it when everyone wants different niche pieces of info logged.

> Log and count failure to obtain requested consistency
> -----------------------------------------------------
>                 Key: CASSANDRA-9191
>                 URL:
>             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

View raw message