[jira] [Updated] (CASSANDRA-17619) Expired snapshots of dropped tables are not removed after node restart

["Paulo Motta (Jira)" <ji...@apache.org>]

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

Paulo Motta updated CASSANDRA-17619:
------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Implementation(12988)
       Complexity: Normal
      Component/s: Local/Snapshots
    Discovered By: User Report
    Fix Version/s: 4.1
         Severity: Normal
         Assignee: Paulo Motta
           Status: Open  (was: Triage Needed)

> Expired snapshots of dropped tables are not removed after node restart
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-17619
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17619
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Snapshots
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>            Priority: Normal
>             Fix For: 4.1
>
>
> Expired TTL snapshots from a dropped table are only removed if the node is not restarted after the table is dropped.
> The reason for this is because {{SnapshotManager}} is using the old implementation of {{listsnapshots}} to load snapshots in memory during node startup, before CASSANDRA-16843 is fixed so it doesn't keep track of snapshots of dropped tables.
> We should make {{SnapshotManager}} use the new implementation to load snapshots of dropped tables in memory, what ensures they will be removed when expired.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org