[ https://issues.apache.org/jira/browse/CASSANDRA-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540879#comment-17540879 ]
Stefan Miklosovic commented on CASSANDRA-17619: ----------------------------------------------- Well ... because it is not fully out yet and Mick just tagged it by -tentative, if he still has some work to do related to releasing, I just do not want to mess with my stuff in the middle. He just tagged it, 4.1-alpha1 is not a branch, right? > 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-beta > > Time Spent: 2h > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org