[
https://issues.apache.org/jira/browse/CASSANDRA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271522#comment-13271522
]
Jonathan Ellis commented on CASSANDRA-3706:
-------------------------------------------
bq. I'm not sure what last_yaml is if we're storing by digest
Why would we do that? Just store the file raw. Then you don't need FS access,
is my point.
bq. also we're backing up 3 different files, not just yaml, but that's not a
big deal
Yeah, I was kind of hoping the extrapolation would be obvious. :P
> 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
>
>
> 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
