[
https://issues.apache.org/jira/browse/CASSANDRA-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611816#comment-14611816
]
Aleksey Yeschenko commented on CASSANDRA-9299:
----------------------------------------------
bq. is it related to your change, if so is there way to restore tombstone
reporting for no system keys?
System keyspaces/tables are not special cased, it's just that in your case they
are the only ones with something to report (I'm assuming one of them is
system.schema_columns). In that case you are fine.
> 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.0.15, 2.1.6
>
> Attachments: 9299-2.0.txt, 9299-2.1.txt, 9299-trunk.txt
>
>
> 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)
