You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pierre-Yves Ritschard (JIRA)" <ji...@apache.org> on 2011/09/12 12:30:09 UTC

[jira] [Issue Comment Edited] (CASSANDRA-2963) Add a convenient way to reset a node's schema

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

Pierre-Yves Ritschard edited comment on CASSANDRA-2963 at 9/12/11 10:30 AM:
----------------------------------------------------------------------------

First try at an apache cassandra patch, the possible problems are the way the futures are handled in SystemTable.java.
I also don't know how to write proper unit test for that type of functionnality.

      was (Author: pyritschard):
    First try at an apache cassandra patch, the possible problems are the way the futures are handled in SystemTable.java 
  
> 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
>            Priority: Minor
>              Labels: lhf
>             Fix For: 0.8.6
>
>         Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira