cassandra-commits mailing list archives

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995962#comment-14995962
] 

Stefania commented on CASSANDRA-10585:
--------------------------------------

I can't say I'm an expert in this part of the code but it shouldn't be too hard to work it
out. I would check with [~slebresne] first however, since it may no longer be relevant with
the new storage engine or he may prefer someone else to look at it.

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