cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3453) cassandra.yaml needs a snapshot_directory setting
Date Sat, 05 Nov 2011 03:33:51 GMT

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

Jonathan Ellis commented on CASSANDRA-3453:
-------------------------------------------

but you still have to have it per keyspace, unless you're willing to throw away the information
of what keyspace it came from, which I'm not.

you also need to have it per data_dir since those could be on different volumes, and hard
links won't work cross-volume.

sounds like a pretty limited win to me.
                
> 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

        

Mime
View raw message