cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-44) It is difficult to modify the set of ColumnFamliies in an existing cluster
Date Fri, 09 Apr 2010 13:43:51 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855394#action_12855394
] 

Hudson commented on CASSANDRA-44:
---------------------------------

Integrated in Cassandra #402 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/402/])
    RingCache fixups in the wake of CASSANDRA-44

 * invoke DatabaseDescriptor.loadSchemas from RingCache ctor (needed
   now to populate DD's table list).
 * improved error handling in DD.getReplicaPlacementStrategyClass so that
   any future failures to call loadSchemas are easier to spot.
 * updated TestRingCache. This was never runnable as a unit test, (it
   requires a running instance), and doing static initialization is
   problematic now that RingCache's ctor throws IOExceptions.

Patch by eevans


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


Mime
View raw message