different query result after a rerun of the same query

Hi all, I'm using Cassandra 3.11.3.5. I have just noticed that when I perform a query I get 0 result but if I launch that same query after few seconds I get the right result. I have traced the query: cqlsh> select event_datetime, id_url, uuid, num_pages from mkp_history.mkp_lookup where id_url=

Re: different query result after a rerun of the same query

You haven’t said what consistency level you are using. CQLSH by default uses consistency level one which may be part of the issue - try using a higher level (eg CONSISTENCY QUOROM). After results are returned correctly are they then returned correctly for all future runs? When was the data inserte

Re: Re: Re: how to configure the Token Allocation Algorithm

Hello Anthony, Effectively I did not start the seed of every rack firsts. Thank you for the post. I believe this is something important to have as official documentation in cassandra.apache.org. This issues as many others are not documented properly. Of course I find the blog of last pickle very

Re: different query result after a rerun of the same query

thank you Ben for the reply. > You haven’t said what consistency level you are using. CQLSH by default uses consistency level one which may be part of the issue - try using a higher level (eg CONSISTENCY QUOROM) yes, actually I used CQLSH so the consistency level was set to ONE. After I changed it

Increasing the size limits implications

Hi, I'm inserting into cassandra in batches(With each containing single PK ).But my batch is failing and throwing exceptions. I want to know if we increase batch_size_warn_threshold_in_kb to 200KB and batch_size_fail_threshold_in_kb to 300KB. What could be potential issues i could be facing

Re: different query result after a rerun of the same query

My guess is the initial query was causing a read repair so, on subsequent queries, there were replicas of the data on every node and it still got returned at consistency one. There are a number of ways the data could have become inconsistent in the first place - eg badly overloaded or down nodes,

Re: Increasing the size limits implications

Increasing batch size could potentially lead to longer GC pauses. Try to break you batch size. 300kb is a decent limit for most use cases. Regards, Nitan Cell: 510 449 9629 > On Apr 29, 2019, at 12:17 PM, Bobbie Haynes wrote: > > Hi, > I'm inserting into cassandra in batches(With each

Re: cassandra node was put down with oom error

Hello, I'm suffering from similar problem with OSS cassandra version3.11.3. My cassandra cluster have been running for longer than 1 years and there was no problem until this year. The cluster is write-intensive, consists of 70 nodes, and all rows have 2 hr TTL. The only change is the read consi