Details
-
New Feature
-
Status: Resolved
-
Low
-
Resolution: Not A Problem
-
None
-
None
-
None
Description
Currently the only option for removing snapshots of dropped column families is to delete them manually from the file system. We have a user that creates column families dynamically and deletes them when they are no longer needed. The result is snapshots of these tables build up quickly and disk space can only be reclaimed when they are manually deleted.
A potential solution for this might be to add a flag to the nodetool clearsnaphot command that removes snapshots that no longer exist in the keyspace because they have been dropped.
Another possibility might be to add a flag on cql delete query that ignores the auto_snapshot in the cassandra.yaml and does not create a snapshot for the deleted column family or keyspace.