cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: drop/recreate column family race condition
Date Tue, 07 Sep 2010 21:24:18 GMT
On Tue, Sep 7, 2010 at 5:10 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
> On Tue, Sep 7, 2010 at 3:55 PM, B. Todd Burruss <bburruss@real.com> wrote:
>> using 0.7 latest from trunk as of few minutes ago.  1 client, 1 node
>>
>> i have the scenario where i want to drop a column family and recreate it -
>> unit testing for instance, is a good reason you may want to do this (always
>> start fresh).
>>
>> the problem i observe is that if i do the following:
>>
>> 1 - drop the column family
>> 2 - recreate it
>> 3 - read data from a key that existed before dropping, but doesn't exist now
>>
>> if those steps happen fast enough, i will get the old row - definitely no
>> good.
>
> old rows can appear until the drop is complete.  as you're aware, this
> is part of the design.
>
>> if they happen slow enough, get_slice throws:
>
> this is definitely a bug.  Can you open a ticket?
>
> BTW, is there a reason you're not using truncate instead of
> drop/recreate?  It's lighter-weight since it doesn't have to do a
> schema migration.
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of Riptano, the source for professional Cassandra support
> http://riptano.com
>

I am using truncate in one of my unit test. I added in a 1 second
sleep after calling it. Does that seem reasonable?

Mime
View raw message