[
https://issues.apache.org/jira/browse/CASSANDRA-21577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105226#comment-18105226
]
Stefan Miklosovic commented on CASSANDRA-21577:
-----------------------------------------------
+1, this should be retrofitted back to 4.0
> Fixes for fully-expired SSTable index notification in compaction
> ----------------------------------------------------------------
>
> Key: CASSANDRA-21577
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21577
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Feature/2i Index, Local/Compaction, Local/Compaction/TWCS
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
>
> In CASSANDRA-20829, secondary index implementations started receiving
> notifications about rows fully expired during compaction. However, this
> change introduced three issues:
> - A read error or a throwing custom indexer aborted the whole compaction.
> Expired SSTables were never obsoleted and every retry hit the same failure.
> - The static row was never passed to removeRow, so static-column indexes
> missed expired-data notifications.
> - NoOpIndex, PaxosUncommittedIndex and RouteJournalIndex inherited the
> default (true) and did no useful work on this path, forcing needless full
> scans of expired SSTables on system.paxos / accord tables. Opt them out
> matching SAI/SASI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
