If you have succesfully run a repair between the initial insert and running
the first select then that should have ensured that all replicas are there.
Are you sure your repairs are completing successfully?
To check if all replicas are not been written during the periods of high
load you can
> 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
got it
>There are a number of ways the data could have become inconsistent in the
first place - eg badly overloaded or
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
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
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
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
