cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-44) It is difficult to modify the set of ColumnFamliies in an existing cluster
Date Tue, 05 Jan 2010 21:45:54 GMT


Jonathan Ellis commented on CASSANDRA-44:

Instead of manually propagating & reconciling schema changes in (3) and (4), we could
add per-keyspace replication factor as suggested in CASSANDRA-620.  We'd still need to gossip
version id so schema changes don't rely on a weekly (for instance) repair operation to be
consistent, but we could still use the repair code that is already done rather than rolling
it manually.

> It is difficult to modify the set of ColumnFamliies in an existing cluster
> --------------------------------------------------------------------------
>                 Key: CASSANDRA-44
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Eric Evans
>            Assignee: Gary Dusbabek
>             Fix For: 0.9
> ColumnFamilies may be added when cassandr is not running by editing the configuration
> 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.

View raw message