[ https://issues.apache.org/jira/browse/CASSANDRA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3706. --------------------------------------- Resolution: Won't Fix Fix Version/s: (was: 2.0) Reviewer: (was: brandon.williams) I think the discomfort we ran into here is a good sign that this is something better managed outside of C*. > 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 > Attachments: save_configuration_2.diff, save_configuration_3.diff, > save_configuration_4.diff, save_configuration_6.diff, > save_configuration_7.diff, save_configuration_8.diff, > save_configuration_9.diff, save_configuration.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 For more information on JIRA, see: http://www.atlassian.com/software/jira