[
https://issues.apache.org/jira/browse/CASSANDRA-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985346#comment-14985346
]
Chris Burroughs commented on CASSANDRA-10023:
---------------------------------------------
I think these would be more useful as Meter (like timeouts & failures) instead
of just all time counters. For example it would be easy to answer at a glance
"are token aware clients working as expected" or "what is the ratio of local to
remote reads since $BAD_PERF_THING happened".
> Emit a metric for number of local read and write calls
> ------------------------------------------------------
>
> Key: CASSANDRA-10023
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10023
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Assignee: Tushar Agrawal
> Priority: Minor
> Labels: lhf
> Attachments: 0001-CASSANDRA-10023.patch
>
>
> Many C* drivers have feature to be replica aware and chose the co-ordinator
> which is a replica. We should add a metric which tells us whether all calls
> to the co-ordinator are replica aware.
> We have seen issues where client thinks they are replica aware when they
> forget to add routing key at various places in the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
