cate
keys in IN.
On Thu, Feb 4, 2016 at 3:48 PM, Edouard COLE
mailto:edouard.c...@rgsystem.com>> wrote:
Hello,
When running that kind of query with TRACING ON; I noticed the coordinator is
also performing multiple time the same query
Because the element in the IN statement can involve man
ard COLE
De : Alain RODRIGUEZ [mailto:arodr...@gmail.com]
Envoyé : Thursday, February 04, 2016 11:55 AM
À : Edouard COLE
Cc : user@cassandra.apache.org
Objet : Re: Duplicated key with an IN statement
Hi,
This is interesting.
It seems rational that if you are looking at 2 keys and both exist (which
t WHERE key IN (123, 123);
key | value
-+---
123 | 456
123 | 456 <- WTF?
(2 rows)
Adding multiple time the same key into an IN statement make the query returns
multiple time the tuple
This looks weird to me, can anyone give me some feedback on such a behavior?
Edouard COLE
Hi,
Could you show us how you measure CPU & network?
Just to be sure we're not missing something obvious
Thanks,
De : Alain RODRIGUEZ [mailto:arodr...@gmail.com]
Envoyé : Monday, September 07, 2015 5:19 PM
À : user@cassandra.apache.org
Objet : Re: Effect of adding/removing nodes from cassand
233dc2-a8ae-4c00-af74-0a119825237f RAC1
the result of the query select * from service_dictionary.table1; gave me
70 rows from 40.0.0.205
64 from 40.0.0.209
54 from 40.0.0.208
2015-09-07 11:13 GMT+02:00 Edouard COLE :
Could you provide the result of :
- nodetool status
- nodetool status YOURKEYSPACE
Could you provide the result of :
- nodetool status
- nodetool status YOURKEYSPACE
@ibrahim: When saying "clocks should be synchronized", it includes Cassandra
nodes AND clients
NTP is the way to go
Le 6 sept. 2015 à 14:56, Laing, Michael
mailto:michael.la...@nytimes.com>> a écrit :
https://en.wikipedia.org/wiki/Network_Time_Protocol
On Sun, Sep 6, 2015 at 8:23 AM, ibrahim
compaction strategy from STCS to DTCS, and it rocks!
I hope this message will help someone someday,
Edouard COLE
tags: secondary index join stuck timeout thrift feedback random repair
