cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14870) The order of application of nodetool garbagecollect is broken
Date Wed, 07 Nov 2018 12:36:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Branimir Lambov updated CASSANDRA-14870:
----------------------------------------
    Reviewer: ZhaoYang
      Status: Patch Available  (was: Open)

Patch for 3.11 linked, applies with insignificant changes to master too. Incorporates CASSANDRA-14099
as that required the same change of order.
The LCS ordering test (by [~VincentWhite]) is copied from the CASSANDRA-14099 patch.

> 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
>            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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message