cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Kogan <pavel.ko...@cortica.com>
Subject Re: Using Cassandra as cache
Date Mon, 23 Jun 2014 17:45:29 GMT
Thank you all,

The issue was resolved (or more exactly bypassed) by adding small python
script running hourly in cron on 1-2 nodes, which pre-provision next hour
keyspace. One hour is definitely enough time for scheme propagation.

Regards,
  Pavel


On Sun, Jun 22, 2014 at 9:35 AM, Robert Stupp <snazy@snazy.de> wrote:

>
> Am 21.06.2014 um 00:37 schrieb Pavel Kogan <pavel.kogan@cortica.com>:
>
> > Thanks,
> >
> > Is there any code way to know when the scheme finished to settle down?
>
> Yep - take a look at
> com.datastax.driver.core.ControlConnection#waitForSchemaAgreement in the
> Java Driver source. It basically compares the 'schema_version' column in
> system.peers against the 'schema_version' column in system.local until
> there's only one distinct value.
>
> > Can working RF=2 and CL=ANY result in any problem with consistency? I am
> not sure I can have problems with consistency if I don't do updates, only
> writes and reads. Can I?
>
> Why should it? CL ANY allows you to push updates without the requirement
> that the node(s) that own the key need to be up. Although you do not have
> the guarantee that reads will immediately show the updates. BTW updates =
> insert = upsert ;)
>
> > By the way I am using Cassandra 2.0.8.
>
>

Mime
View raw message