cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3706) Back up configuration files on startup
Date Wed, 09 May 2012 16:51:50 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271583#comment-13271583
] 

Dave Brosius commented on CASSANDRA-3706:
-----------------------------------------

currently the rows are keyed by ip address, and have columns

YAMLDIGEST, YAMLCONTENTS, LOG4JDIGEST, LOG4JCONTENTS, ENVDIGEST, ENVCONTENTS

the digest columns are so you don't constantly write duplicate 'blobs' into the database if
nothing has changed. perhaps that's not much of a concern and i may be biased by the fact
that i constant start and stop instances for debugging.

In any case, i can change it to whatever you like.


                
> 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

        

Mime
View raw message