cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2963) Add a convenient way to reset a node's schema
Date Mon, 02 Jul 2012 23:33:57 GMT

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

Pavel Yaskevich commented on CASSANDRA-2963:
--------------------------------------------

Looking back I think that this was does because due to the nature of clear operation when
we receive data from remove node (keyspace + nested cfs) and initialize keyspace we would
also initCf each of the CF impicitly in new Table(...) so by it's nature merge operation doesn't
really know if any cfs were already initialized (by re-creating keyspace for example) it would
just call initCf for each of the new cfs again and to avoid any order preserving or checking
if cf was already initialized we just try to reload attributes if it is already present in
the Table.columnFamilyStores.
                
> 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.0
>
>         Attachments: CASSANDRA-2963-v3.patch, cassandra-1.1-2963-v2.txt, 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