You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Lohfink (JIRA)" <ji...@apache.org> on 2015/01/13 17:38:35 UTC
[jira] [Commented] (CASSANDRA-7338) CFS.getRangeSlice should update
latency metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275507#comment-14275507 ]
Chris Lohfink commented on CASSANDRA-7338:
------------------------------------------
Could we actually include the EstimatedHistogram version that was cut out in v3? The Metrics histogram is pretty bad at non-normal data like latencies and (empirically tested and theoretically) is untrustworthy at 99th percentile. For applications that care about the percentiles having the more statistically accurate version is beneficial.
> CFS.getRangeSlice should update latency metrics
> -----------------------------------------------
>
> Key: CASSANDRA-7338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7338
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Trivial
> Fix For: 2.1 rc2
>
> Attachments: 7338-3.txt, CASSANDRA-7338-v2.txt, CASSANDRA-7338.txt
>
>
> CFS.getRangeSlice doesn't update the CF readLatency metric in the same way as CFS.getColumnFamily does.
> I may be missing something, but I couldn't see a good reason why this wasn't already the case as without it, "SELECT * FROM t WHERE x=y" results in the read metrics being incremented, but "SELECT * FROM t" doesn't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)