cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Burmistrov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10585) SSTablesPerReadHistogram seems wrong when row cache hit happend
Date Sat, 21 Nov 2015 12:58:11 GMT


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:
>             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
> 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

View raw message