You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ivan Burmistrov (JIRA)" <ji...@apache.org> on 2015/12/02 17:56:11 UTC
[jira] [Commented] (CASSANDRA-10585) SSTablesPerReadHistogram seems
wrong when row cache hit happend
[ https://issues.apache.org/jira/browse/CASSANDRA-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036122#comment-15036122 ]
Ivan Burmistrov commented on CASSANDRA-10585:
---------------------------------------------
I've attached patch for trunk (and it works for 3.0 too).
> 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
> Assignee: Ivan Burmistrov
> Priority: Minor
> Fix For: 2.1.x, 2.2.x, 3.0.x
>
> Attachments: SSTablePerReadHistogram_RowCache-cassandra-2_1.patch, SSTablePerReadHistogram_RowCache-cassandra-2_2.patch, SSTablePerReadHistogram_RowCache_trunk.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)