[
https://issues.apache.org/jira/browse/CASSANDRA-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020444#comment-15020444
]
Ivan Burmistrov commented on CASSANDRA-10585:
---------------------------------------------
I've reattached patch for 2.2: I've added the ability to consider 0 values in
EstimatedHistogram and SSTablesPerReadHistogram uses this ability now.
If it is OK, I will prepare patches for 3.0 and trunk.
> 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, 2.2.x, 3.0.x
>
> Attachments: SSTablePerReadHistogram_RowCache-cassandra-2_1.patch,
> SSTablePerReadHistogram_RowCache-cassandra-2_2.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)
