You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (Created) (JIRA)" <ji...@apache.org> on 2011/11/03 22:51:32 UTC

[jira] [Created] (CASSANDRA-3453) cassandra.yaml needs a directory_setting

cassandra.yaml needs a 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

        

[jira] [Commented] (CASSANDRA-3453) cassandra.yaml needs a snapshot_directory setting

Posted by "Matthew F. Dennis (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Resolved] (CASSANDRA-3453) cassandra.yaml needs a snapshot_directory setting

Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-3453.
---------------------------------------

    Resolution: Won't Fix

The complexity I'm referring to is from the user's point of view.  Especially in a cluster setting if you forget to update it on a new machine it can really cause a head-scratching moment.  It doesn't sound like it's worth it 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

        

[jira] [Updated] (CASSANDRA-3453) cassandra.yaml needs a snapshot_directory setting

Posted by "Matthew F. Dennis (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew F. Dennis updated CASSANDRA-3453:
-----------------------------------------

    Summary: cassandra.yaml needs a snapshot_directory setting  (was: cassandra.yaml needs a directory_setting)
    
> 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

        

[jira] [Commented] (CASSANDRA-3453) cassandra.yaml needs a directory_setting

Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143648#comment-13143648 ] 

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

What is the benefit of this in exchange for the complexity of having to check a setting now to find out where your snapshots are?
                
> cassandra.yaml needs a 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

        

[jira] [Commented] (CASSANDRA-3453) cassandra.yaml needs a snapshot_directory setting

Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Commented] (CASSANDRA-3453) cassandra.yaml needs a snapshot_directory setting

Posted by "Brandon Williams (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144565#comment-13144565 ] 

Brandon Williams commented on CASSANDRA-3453:
---------------------------------------------

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

With CASSANDRA-2749 landing soon I too don't see how this can provide any value.
                
> 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

        

[jira] [Commented] (CASSANDRA-3453) cassandra.yaml needs a directory_setting

Posted by "Matthew F. Dennis (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144384#comment-13144384 ] 

Matthew F. Dennis commented on CASSANDRA-3453:
----------------------------------------------

1) It is easier to backup/copy all your snapshots for all keyspaces if they are in one place instead of having to iterate over all the keyspace directories looking for the snapshot directories.

2) it is safer when deleting snapshots (less chance of scripts/admins accidentally deleting the keyspace instead of all the snapshots. (e.g. rm -rf /some/path/$ksname/snapshots/* where $ksname ends up a blank space because of a script bug)
 
besides, checking a setting isn't very complex code wise ;)
                
> cassandra.yaml needs a 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