[ https://issues.apache.org/jira/browse/CASSANDRA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190141#comment-13190141 ]
Brandon Williams commented on CASSANDRA-3706: --------------------------------------------- This looks good, but a couple of things: using the IP address as the row key can make things a bit painful if the machine changes IPs. Is there any reason not to use a hardcoded, predictable key such as "CONFIG" or something similar? In a similar vein, a column for both the digest and the content seems like a bit much, couldn't we store the digest as the column name and the contents at the value? Finally, if we do use a static row key, an entire new CF for this seems like overkill, we could just stuff this into the STATUS_CF. > 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 > > Attachments: save_configuration.diff, save_configuration_2.diff, > save_configuration_3.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