[jira] [Commented] (CASSANDRA-10585) SSTablesPerReadHistogram seems wrong when row cache hit happend

["Jim Witschey (JIRA)" <ji...@apache.org>]

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

Jim Witschey commented on CASSANDRA-10585:
------------------------------------------

[~benedict] or [~Stefania], is one of you the right person to have a look at this?

> SSTablesPerReadHistogram seems wrong when row cache hit happend
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-10585
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10585
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ivan Burmistrov
>            Priority: Minor
>             Fix For: 2.1.x
>
>         Attachments: cassandra-10585.patch
>
>
> SSTablePerReadHistogram metric now not considers case when row has been read from row cache.
> And so, this metric will have big values even almost all requests processed by row cache (and without touching SSTables, of course).
> So, it seems that correct behavior is to consider that if we read row from row cache then we read zero SSTables by this request.
> The patch at the attachment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)