cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3706) Back up configuration files on startup
Date Fri, 20 Jan 2012 21:50:40 GMT


Dave Brosius commented on CASSANDRA-3706:

I was assuming that there would n rows in this CF, one per cluster member, each with it's
own yaml. This calls for a non hard coded key, unless you want to make n columns for each

As for the digest as the column name, when the yaml changes and you want to update the contents
in the row, you would want to remove the old column, but you don't really know what the old
column name is now. Perhaps you could just delete columns that you don't know what they are
but that seems a little iffy to me.

> Back up configuration files on startup
> --------------------------------------
>                 Key: CASSANDRA-3706
>                 URL:
>             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,, and maybe on
startup, we can back them up to a columnfamily that can then be handled by normal snapshot/backup

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message