I thought it went without saying that if you plan to drop a CF, you should stop using it before you drop it.
On Tue, Sep 7, 2010 at 12:28 PM, Rob Coli <rc...@digg.com> wrote: > On 9/7/10 10:09 AM, Jonathan Ellis wrote: >> >> flush, stop server, remove the data files, start server > > As I understand it, there a race here where a new Memtable can be created > before the server is stopped, unless you flush with "nodetool drain". This > is relevant in some versions of 0.6.x (below 0.6.3? 0.6.4?) which will barf > and deadlock on a commitlog containing a CF which is not (no longer) defined > in storage-conf.xml. Versions after that just ignore that statement in the > commitlog. > > =Rob > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
