[
https://issues.apache.org/jira/browse/CASSANDRA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271567#comment-13271567
]
Jonathan Ellis commented on CASSANDRA-3706:
-------------------------------------------
Okay, let me spell it out a bit more:
{code}
last_yaml = None
for yaml in query("select yaml from backups"):
if last_yaml != None and yaml != last_yaml:
raise 'cluster yaml out of sync'
last_yaml = yaml
{code}
... that said, it would make sense to me to to use a data model like this:
{code}
CREATE TABLE config_backups (
peer inetaddress,
backed_up_at datetime,
cassandra_yaml text,
cassandra_env text,
PRIMARY KEY (peer, backed_up_at)
)
{code}
which would allow you to query history for a given node (at the cost of making
my example loop for "compare current versions" more complex, since CQL isn't
powerful enough to say "give me the most recent version for each node" --
although you could do that with Hive).
(could this use our new-fangled gossip node id instead of the ip?)
> 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
