You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/09/11 22:38:57 UTC
[jira] Updated: (CASSANDRA-44) It is difficult to modify the set of
ColumnFamliies in an existing cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-44:
------------------------------------
Description:
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
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
was:
ColumnFamilies may be added when cassandr is not running by editing the configuration file. When doing this they should ONLY BE ADDED AT THE END OF THE LIST OF EXISTING FAMILIES.
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
> 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
> Fix For: 0.5
>
>
> 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
> 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.