cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-44) It is difficult to modify the set of ColumnFamliies in an existing cluster
Date Mon, 02 Nov 2009 04:24:59 GMT

     [ 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

Alternatively on Cassandra 0.4.2 or later:
1) run nodeprobe flush and wait for it to finish
2) kill cassandra

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.

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
>
> 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
> 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.


Mime
View raw message