[
https://issues.apache.org/jira/browse/CASSANDRA-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Stepura resolved CASSANDRA-6418.
----------------------------------------
Resolution: Fixed
Let's use CASSANDRA-6821 fro that
> auto_snapshots are not removable via 'nodetool clearsnapshot'
> -------------------------------------------------------------
>
> Key: CASSANDRA-6418
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6418
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: auto_snapshot: true
> Reporter: J. Ryan Earl
> Assignee: Lyuben Todorov
> Priority: Minor
> Fix For: 2.0.5
>
> Attachments: 6418_cassandra-2.0.patch, 6418_cassandra-2.0_v5.patch,
> 6418_v2.patch, 6418_v3_cassandra-2.0.patch, CASSANDRA-2.0-6418_v4.patch
>
>
> Snapshots of deleted CFs created via the "auto_snapshot" configuration
> parameter appear to not be tracked. The result is that 'nodetool
> clearsnapshot <keyspace with deleted CFs>' does nothing, and short of
> manually removing the files from the filesystem, deleted CFs remain
> indefinitely taking up space.
> I'm not sure if this is intended, but it seems pretty counter-intuitive. I
> haven't found any documentation that indicates "auto_snapshots" would be
> ignored by 'nodetool clearsnapshot'.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
