[
https://issues.apache.org/jira/browse/CASSANDRA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848409#action_12848409
]
Gary Dusbabek commented on CASSANDRA-44:
----------------------------------------
It won't be hard to handle as long as the downed node doesn't participate in
writes until it's schema is stable. rename(A,B) is migration0, add(A) is
migration1. migration1 won't be applied to N because it realizes it isn't
migrating from migration0 (migration1 specifies that it is a migration from
migration0). N quickly realizes it is using an older version of the schema, it
requests all the versions it is missing and then applies them in order
(migration0, migration1).
> It is difficult to modify the set of ColumnFamliies in an existing cluster
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-44
> URL: https://issues.apache.org/jira/browse/CASSANDRA-44
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Eric Evans
> Assignee: Gary Dusbabek
> Fix For: 0.7
>
>
> ColumnFamilies may be added when cassandr is not running by editing the
> configuration file.
> If you need to delete or re-order CFs, you must
> 1) kill cassandra
> 2) start it again and wait for log replay to finish
> 3) kill cassandra AGAIN
> Alternatively on Cassandra 0.4.2 or later:
> 1) run nodeprobe flush and wait for it to finish
> 2) kill cassandra
> Then:
> 4) make your edits (now there is no data in the commitlog)
> 5) manually remove the sstable files (-Data.db, -Index.db, and -Filter.db)
> for the CFs you removed, and rename files for CFs you renamed
> 6) start cassandra and your edits should take effect
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
