cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michał Łowicki <mlowi...@gmail.com>
Subject Re: Timeouts but returned consistency level is invalid
Date Fri, 30 Jan 2015 13:37:29 GMT
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 <cnet62@yahoo.com> wrote:

> 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 ?
>
> cheers
> Jan
>
> C* Architect
>
>
>   On Friday, January 30, 2015 1:36 AM, Michał Łowicki <mlowicki@gmail.com>
> wrote:
>
>
> 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 out waiting for replica nodes' responses] message="Operation
timed out - received only 3 responses." info={'received_responses': 3, 'required_responses':
4, 'consistency': 'ALL'}
>
>
> code=1200 [Coordinator node timed out waiting for replica nodes' responses] message="Operation
timed out - received only 1 responses." info={'received_responses': 1, 'required_responses':
2, 'consistency': 'LOCAL_QUORUM'}
>
>
> code=1100 [Coordinator node timed out waiting for replica nodes' responses] message="Operation
timed out - received only 0 responses." info={'received_responses': 0, 'required_responses':
1, 'consistency': 'ONE'}
>
>
> Any idea why it might happen?
>
> --
> BR,
> Michał Łowicki
>
>
>


-- 
BR,
Michał Łowicki

Mime
View raw message