You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/05/05 16:16:00 UTC
[jira] [Updated] (CASSANDRA-9299) Fix counting of tombstones
towards TombstoneOverwhelmingException
[ https://issues.apache.org/jira/browse/CASSANDRA-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-9299:
-----------------------------------------
Assignee: Aleksey Yeschenko
> Fix counting of tombstones towards TombstoneOverwhelmingException
> -----------------------------------------------------------------
>
> Key: CASSANDRA-9299
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9299
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Fix For: 2.1.x, 2.0.x
>
>
> CASSANDRA-6042 introduced warning on too many tombstones scanned, then CASSANDRA-6117 introduced a hard TombstoneOverwhelmingException condition.
> However, at least {{SliceQuerFilter.collectReducedColumn()}} seems to have the logic wrong. Cells that are covered by a range tombstone or a partition high level deletion, still count towards {{ColumnCounter}}'s {{ignored}} register.
> Thus it's possible to have an otherwise healthy (though large) dropped partition read cause an exception that shouldn't be there.
> The only things that should count towards the exception are cell tombstones and range tombstones (CASSANDRA-8527), but never ever live cells shadowed by any kind of tombstone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)