cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10585) SSTablesPerReadHistogram seems wrong when row cache hit happend
Date Mon, 23 Nov 2015 22:33:10 GMT

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

Ariel Weisberg updated CASSANDRA-10585:
---------------------------------------
    Assignee: Ivan Burmistrov

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