cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3706) Back up configuration files on startup
Date Thu, 26 Jan 2012 02:17:40 GMT


Dave Brosius updated CASSANDRA-3706:

    Attachment: save_configuration_6.diff

Move the Configuration column family to a separate system_configuration keyspace that uses
SimpleStrategy and RF=1.

Added a Schema.instance.getSystemTables() method and use that for filtering out client queries.

de-emphasize the use of Table.SYSTEM_TABLE where possible, use the inferred keyspace name.

Very possible i missed something here due to ignorance, so a thorough review would be appreciated.

> 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,
save_configuration_4.diff, save_configuration_6.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