[
https://issues.apache.org/jira/browse/CASSANDRA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147226#comment-15147226
]
Sylvain Lebresne commented on CASSANDRA-9191:
---------------------------------------------
We agree that logging that by default is not a good idea and we already
somewhat log it at debug (which means you can manipulate you per-class log
setting to get it logged if you really wish). The only thing mentioned above
that we don't seem to have is the query itself, but I suppose there won't be
objection to appending the query itself to the debug message if someone
provides a patch.
There is also the issue of exposing a counter, but I think this can be done as
part of CASSANDRA-7384 since that's fairly related and I left a comment
regarding that on the issue.
> Log and count failure to obtain requested consistency
> -----------------------------------------------------
>
> Key: CASSANDRA-9191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9191
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Matt Stump
> Priority: Minor
> Labels: lhf
>
> 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)
