[
https://issues.apache.org/jira/browse/CASSANDRA-14870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685049#comment-16685049
]
Branimir Lambov commented on CASSANDRA-14870:
---------------------------------------------
Committed to 3.11 as
[a03424ef95559c9df2bb7f86e1ac1edca1436058|https://github.com/apache/cassandra/commit/a03424ef95559c9df2bb7f86e1ac1edca1436058]
and trunk as
[b80f6c65fb0b97a8c79f6da027deac06a4af9801|https://github.com/apache/cassandra/commit/b80f6c65fb0b97a8c79f6da027deac06a4af9801].
> The order of application of nodetool garbagecollect is broken
> -------------------------------------------------------------
>
> Key: CASSANDRA-14870
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14870
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Major
>
> {{nodetool garbagecollect}} was intended to work from oldest sstable to
> newest, so that the collection in newer tables can purge tombstones over data
> that has been deleted.
> However, {{SSTableReader.maxTimestampComparator}} currently sorts in the
> opposite order (the order changed in CASSANDRA-13776 and then back in
> CASSANDRA-14010), which makes the garbage collection unable to purge any
> tombstones.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
