cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-44) It is difficult to modify the set of ColumnFamliies in an existing cluster
Date Mon, 21 Sep 2009 15:02:16 GMT


Eric Evans commented on CASSANDRA-44:

> this does push the problem of keeping the config files in sync across nodes onto ops,
but ops would
> probably prefer that to requiring a completely new service piece. :) 

That problem already exists. If you are making additions, removals, or renames, then you are
going to have to sync those changes with the entire cluster. Whether it's a single file or
many doesn't make much of a difference IMO.

Also, if this is implemented with an additional config, then we should probably expose it
through get_string_property() in the same way we do the current configuration (which incidentally
could be useful to ops in syncing up the cluster).

> 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
>             Fix For: 0.5
> 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
> 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