[
https://issues.apache.org/jira/browse/CASSANDRA-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086605#comment-14086605
]
Brandon Williams commented on CASSANDRA-7384:
---------------------------------------------
I too preferred keeping this in the client originally, but after the time I had
tracking CASSANDRA-7567 down, I've changed my mind. It's difficult to be 100%
certain your client is using the consistency level you think it is, and this
can be further complicated by bugs in the driver (I couldn't find it, but I
seem to recall that some driver was sending a different CL than the one
specified at some point.) If you are using a utility like stress that should
be opaque to you, it would be nice to be able to verify it's actually doing
what you think it is. Currently there's no way to do this, since even with
tracing, the CL isn't logged anywhere.
> Collect metrics on queries by consistency level
> -----------------------------------------------
>
> Key: CASSANDRA-7384
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7384
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Vishy Kasar
> Assignee: sankalp kohli
> Priority: Minor
>
> We had cases where cassandra client users thought that they were doing
> queries at one consistency level but turned out to be not correct. It will be
> good to collect metrics on number of queries done at various consistency
> level on the server. See the equivalent JIRA on java driver:
> https://datastax-oss.atlassian.net/browse/JAVA-354
--
This message was sent by Atlassian JIRA
(v6.2#6252)
