You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Laura Adney (JIRA)" <ji...@apache.org> on 2014/05/20 18:34:40 UTC

[jira] [Commented] (CASSANDRA-7023) Nodetool clearsnapshot should not remove all snapshots by default

    [ https://issues.apache.org/jira/browse/CASSANDRA-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003597#comment-14003597 ] 

Laura Adney commented on CASSANDRA-7023:
----------------------------------------

Want to add another point (business scenario) to this.

When using snapshots for backup, administrators might do the following:

Take a snapshot, for tape backups
Repairs running at the same time, which adds an additional snapshot
Do tape backup
Clear snapshot 

The process runs the risk of removing a snapshot used for repairs as well as adding unwanted space to the backup.  The process here is to help manage disk space in a manner that doesn't require a lot of complexity or additional management for snapshots created for repair versus snapshots created for backup.

It would streamline the clear snapshot process to be able to exclude those snapshots that repair is using.   

> Nodetool clearsnapshot should not remove all snapshots by default
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-7023
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7023
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Sucwinder Bassi
>            Priority: Minor
>
> Running a nodetool clearsnapshot will remove all snapshot files by default. As this is removing data this shouldn't just go away and just remove all snapshots. If you want to remove all snapshots there should be a force option. A list option showing snapshots available would also be helpful which could be piped into the nodetool clearsnapshot command.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)