cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2963) Add a convenient way to reset a node's schema
Date Fri, 17 Feb 2012 09:39:59 GMT


Pavel Yaskevich updated CASSANDRA-2963:

    Attachment: CASSANDRA-2963-v3.patch

I have made some styling improvements and changed MigrationManager.resetLocalSchema() to reset
local schema even if there no nodes around (because when the new nodes will come up it will
request schema from them anyway) + I have made sure that if there any nodes schema is requested
from the first node with version >= 1.1.
> Add a convenient way to reset a node's schema
> ---------------------------------------------
>                 Key: CASSANDRA-2963
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Brandon Williams
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1.1
>         Attachments: CASSANDRA-2963-v3.patch, cassandra-1.1-2963-v2.txt, cassandra-1.1-2963.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:!default.jspa
For more information on JIRA, see:


View raw message