cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7338) CFS.getRangeSlice should update latency metrics
Date Wed, 04 Jun 2014 07:08:01 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017444#comment-14017444
] 

Sam Tunnicliffe commented on CASSANDRA-7338:
--------------------------------------------

[~iamaleksey] that wfm, felt a bit weird adding new stuff to the mbean and immediately deprecating
it, but the wanted to keep it consistent in case we decided to add the new stuff to nodetool
cfstats before moving it to the new metrics. Anyway v3 is fine for me, thanks.

> 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.0.9
>
>         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.2#6252)

Mime
View raw message