Thanks Philip. This explains why I see ALL. Any idea why sometimes ONE is
returned?
—
Michał
On Fri, Jan 30, 2015 at 4:18 PM, Philip Thompson
wrote:
> Jan is incorrect. Keyspaces do not have consistency levels set on them.
> Consistency Levels are always set by the client. You are almost certa
Jan is incorrect. Keyspaces do not have consistency levels set on them.
Consistency Levels are always set by the client. You are almost certainly
running into https://issues.apache.org/jira/browse/CASSANDRA-7947 which is
fixed in 2.1.3 and 2.0.12.
On Fri, Jan 30, 2015 at 8:37 AM, Michał Łowicki w
Hi Jan,
I'm using only one keyspace. Even if it defaults to ONE why sometimes ALL
is returned?
On Fri, Jan 30, 2015 at 2:28 PM, Jan wrote:
> HI Michal;
>
> The consistency level defaults to ONE for all write and read operations.
> However consistency level is also set for the keyspace.
>
> Coul
HI Michal;
The consistency level defaults to ONE for all write and read operations.
However consistency level is also set for the keyspace.
Could it be possible that your queries are spanning multiple keyspaces which
bear different levels of consistency ?
cheersJan
C* Architect
On Frida
Hi,
We're using C* 2.1.2, django-cassandra-engine which in turn uses cqlengine.
LOCAL_QUROUM is set as default consistency level. From time to time we get
timeouts while talking to the database but what is strange returned
consistency level is not LOCAL_QUROUM:
code=1200 [Coordinator node timed o
