cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3706) Back up configuration files on startup
Date Thu, 10 May 2012 19:48:52 GMT

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

Brandon Williams commented on CASSANDRA-3706:
---------------------------------------------

If we're going to push this to 1.2 (since your patch is against trunk) then using the new
node id instead of the broadcast address would be nice, otherwise can you rebase to 1.1? 
Between the two, I think I'd rather put this in 1.2, since node id seems like the optimal
way to do this, as changing all the IPs in a cluster is actually not all that uncommon.
                
> Back up configuration files on startup
> --------------------------------------
>
>                 Key: CASSANDRA-3706
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3706
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Dave Brosius
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1.1
>
>         Attachments: save_configuration.diff, save_configuration_2.diff, save_configuration_3.diff,
save_configuration_4.diff, save_configuration_6.diff, save_configuration_7.diff, save_configuration_8.diff
>
>
> Snapshot can backup user data, but it's also nice to be able to have known-good configurations
saved as well in case of accidental snafus or even catastrophic loss of a cluster.  If we
check for changes to cassandra.yaml, cassandra-env.sh, and maybe log4j-server.properties on
startup, we can back them up to a columnfamily that can then be handled by normal snapshot/backup
procedures.

--
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