cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Burmistrov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10585) SSTablesPerReadHistogram seems wrong when row cache hit happend
Date Fri, 23 Oct 2015 18:17:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ivan Burmistrov updated CASSANDRA-10585:
----------------------------------------
     Attachment: cassandra-10585.patch
    Description: 
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.

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



> 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
>          Components: Core
>            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)

Mime
View raw message