[
https://issues.apache.org/jira/browse/CASSANDRA-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685644#comment-15685644
]
Mahdi Mohammadi edited comment on CASSANDRA-12922 at 11/22/16 4:24 AM:
-----------------------------------------------------------------------
||trunk|3.X||
|[branch|https://github.com/apache/cassandra/compare/trunk...mm-binary:trunk-12922]|[branch|https://github.com/apache/cassandra/compare/trunk...mm-binary:12922-3.X]|
was (Author: mahdix):
||trunk|3.X||
|[branch|https://github.com/apache/cassandra/compare/trunk...mm-binary:trunk-12922]|
|[branch|https://github.com/apache/cassandra/compare/trunk...mm-binary:12922-3.X]|
> Bloom filter miss counts are not measured correctly
> ---------------------------------------------------
>
> Key: CASSANDRA-12922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12922
> Project: Cassandra
> Issue Type: Bug
> Reporter: Branimir Lambov
> Assignee: Mahdi Mohammadi
>
> Bloom filter hits and misses are evaluated incorrectly in
> {{BigTableReader.getPosition}}: we properly record hits, but not misses. In
> particular, if we don't find a match for a key in the index, which is where
> almost all non-matches will be rejected, [we don't record a bloom filter
> false
> positive|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/big/BigTableReader.java#L228].
> This leads to very misleading output from e.g. {{nodetool tablestats}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
