[
https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144423#comment-13144423
]
Matthew F. Dennis commented on CASSANDRA-3453:
----------------------------------------------
we provide a setting for controlling the data directories, which is currently a
parent of all the snapshots directories, so you already have the referenced
problems (i.e. checking a setting to find out where your snapshots are and
potentially forgetting to update it on a new machine).
Furthermore, if I have N out of M keyspaces I want to snapshot and backup (or
bulk load to another cluster or ...) after the snapshot I have to remember each
keyspace so I can then construct a path to each snapshot (e.g.
/path/from/data_dir/setting/$ks_name/snapshots/$snapshot_name) in order to do
what I wanted to do with the snapshots instead of knowing everything I care
about is in one place (e.g. /path/from/snapshot_dir/setting/$snapshot_name).
> cassandra.yaml needs a snapshot_directory setting
> -------------------------------------------------
>
> Key: CASSANDRA-3453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3453
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Matthew F. Dennis
>
> cassandra.yaml really needs a config option for a snapshot directory. by
> default it should be a peer folder with saved_caches, commitlog and data.
> assuming the value of that setting is /some/path/snapshot_dir then snapshots
> would go into: /some/path/snapshot_dir/snapshot_name/keyspace_name/
> this makes automation, particularly around backups, much easier and gives
> more control to ops
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
