[
https://issues.apache.org/jira/browse/CASSANDRA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266931#comment-13266931
]
Jonathan Ellis commented on CASSANDRA-3706:
-------------------------------------------
bq. If each node only stores its own config and you backup a snapshot of the
node, you can restore it
The reason I think this probably doesn't belong node-local is, using a standard
replicated CF makes it trivial for any normal client to connect to the cluster
and say, "show me the config for node X," or, "query all backed-up config
files, and make sure they are in sync."
The first, single-node query is only a little harder with node-local storage
(you need to defeat your client's connection pool, and connect to the right
node), but this second is much more difficult: first you need to load a list of
cluster members somehow, then connect to each and query in turn. Vs just doing
a seq scan on a normal, non-node-local config CF to grab them all at once.
> 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
