incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Lebresne <sylv...@datastax.com>
Subject Re: are asynchronous schema updates possible ?
Date Fri, 07 Sep 2012 15:39:34 GMT
> +1 What kinds of problems?

Cassandra uses identifier internally for each CF. If you concurrently
create CFs, you might end up with either two different CFs having the
same identifier or the same CF having two different identifiers (on
two different nodes). That in turn might likely trigger a number of
exceptions server side and could be rather painful to fix.

So do not do it. Not until 1.2 at least.

--
Sylvain

> Thanks,
> Dean
>
> From: Илья Шипицин <chipitsine@gmail.com<mailto:chipitsine@gmail.com>>
> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Tuesday, September 4, 2012 1:12 PM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Subject: Re: are asynchronous schema updates possible ?
>
>
> what kind of  problems?
>
> "nodes do not agree about schema" exception on later node ? something worse?
>
> 2012/9/5 Sylvain Lebresne <sylvain@datastax.com<mailto:sylvain@datastax.com>>
> On Tue, Sep 4, 2012 at 8:23 PM, Илья Шипицин <chipitsine@gmail.com<mailto:chipitsine@gmail.com>>
wrote:
>> Is it ok multiple servers will create/update the same CF at once ? I'm
>> looking into dynamic schema update during application deploy/update.
>
> As said above, it is ok for update the same CF concurrently in 1.1 but
> *not* for creation (if you create CF concurrently, whether that is the
> same CF or not, you might have problem). The last part will be fixed
> in 1.2 however.
>
> --
> Sylvain
>
>>
>> вторник, 4 сентября 2012 г. пользователь Sylvain Lebresne
писал:
>>
>>> To add to Aaron response, you can update a CF concurrently in 1.1
>>> already. However, you cannot create multiple CF concurrently just yet,
>>> but that will be fixed in 1.2.
>>>
>>> --
>>> Sylvain
>>>
>>> On Sun, Aug 26, 2012 at 11:04 PM, aaron morton <aaron@thelastpickle.com<mailto:aaron@thelastpickle.com>>
>>> wrote:
>>> > Concurrent schema changes are coming in 1.2.
>>> >
>>> > I could not find a single issue that covered it, that may be my bad
>>> > search
>>> > fu. The issues for 1.2 are here
>>> > https://issues.apache.org/jira/browse/CASSANDRA/fixforversion/12319262
>>> >
>>> > Cheers
>>> >
>>> > -----------------
>>> > Aaron Morton
>>> > Freelance Developer
>>> > @aaronmorton
>>> > http://www.thelastpickle.com
>>> >
>>> > On 24/08/2012, at 7:06 PM, Илья Шипицин <chipitsine@gmail.com<mailto:chipitsine@gmail.com>>
wrote:
>>> >
>>> > Hello!
>>> >
>>> > we are looking into concurent schema updates (when multiple instances of
>>> > application create CFs at once.
>>> >
>>> > at the http://wiki.apache.org/cassandra/MultiTenant there's open ticket
>>> > 1391, it is said it is still open.
>>> > however, in jura is said "1.1.0 is fixed"
>>> >
>>> > can schema be updated asynchrously on 1.1.x ? or not ?
>>> > if multiple server create the same CF ?
>>> >
>>> > Cheers,
>>> > Ilya Shipitsin
>>> >
>>> >
>

Mime
View raw message