[
https://issues.apache.org/jira/browse/CASSANDRA-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400410#comment-17400410
]
Paulo Motta commented on CASSANDRA-16843:
-----------------------------------------
bq. For trunk I think we should probably refactor snapshot handling altogether
to dissolve the marriage between CFs and snapshots a bit, but for existing
versions I'm not sure what the least invasive way of reworking this is yet.
We've been going towards this direction on CASSANDRA-16451 by centralizing
snapshot management on a `SnapshotManager` module decoupled from CFS, but so
far restricted to snapshots created with TTL. Myself and [~stefan.miklosovic]
plan to extend this to "legacy" snapshots after that work is finished which
will make it easier to solve this issue on trunk/4.1.
> auto-snapshots for dropped tables don't appear in nodetool listsnapshots
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-16843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16843
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
> Reporter: James Brown
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> Auto snapshots from dropped tables don't seem to show up in {{nodetool
> listsnapshots}} (even though they do get cleared by {{nodetool
> clearsnapshot}}). This makes them kind of annoying to clean up, since you
> need to muck about in the data directory to find them.
> Erick on the mailing list said that this seems to be an oversight and that
> clearsnapshot was fixed by
> [CASSANDRA-6418|https://issues.apache.org/jira/browse/CASSANDRA-6418].
> I reproduced this both on 3.11.11 and 4.0.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
