[
https://issues.apache.org/jira/browse/CASSANDRA-17619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543056#comment-17543056
]
Stefan Miklosovic commented on CASSANDRA-17619:
-----------------------------------------------
I run the tests like 50 times, the same one
https://github.com/instaclustr/cassandra/commit/7017450d092f7a111239020fca5d7b76529239ee
Basically, some snapshot operation was done via nodetool and then it was
asserting some state but it was not done yet / it was / was not in the output
and it was throwing exceptions. I had to rewrite it like we are waiting for
some state to happen.
> 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: [email protected]
For additional commands, e-mail: [email protected]
