cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2963) Add a convenient way to reset a node's schema
Date Wed, 01 Feb 2012 16:20:58 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yuki Morishita updated CASSANDRA-2963:
--------------------------------------

    Attachment: cassandra-1.1-2963.txt

In this patch, I add the way to reset Schema after truncating schema_* CF, and then send migration
request to other live node.
I'm not sure if I do the right way for last part (migration request), so please let me know
if I did wrong.

                
> Add a convenient way to reset a node's schema
> ---------------------------------------------
>
>                 Key: CASSANDRA-2963
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2963
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Brandon Williams
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1
>
>         Attachments: cassandra-1.1-2963.txt, system_reset_schema.txt
>
>
> People often encounter a schema disagreement where just one node is out of sync.  To
get it back in sync, they shutdown the node, move the Schema* and Migration* files out of
the system ks, and then start it back up.  Rather than go through this process, it would be
nice if you could just tell the node to reset its schema.

--
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