[
https://issues.apache.org/jira/browse/CASSANDRA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786386#comment-16786386
]
Shaurya Gupta commented on CASSANDRA-9191:
------------------------------------------
Hi,
I have uploaded patches for trunk and 3.11.3 branches (will change to 3.11.x if
required). Please have a look. I'm a bit new to Cassandra code base, please
bear with me if I made some rookie mistake.
Thanks
[~mstump], [~slebresne]
> 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
> Components: Legacy/Coordination, Legacy/Observability
> Reporter: Matt Stump
> Priority: Minor
> Labels: lhf
> Attachments: patch_CASSANDRA-9191_trunk, patch_CASSANDRA-9191_v3.11.3
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
