In this case I was not thinking about what was happening synchronous to client
request, only that the request was hitting all nodes.
You are right, when reading at LOCAL_ONE the coordinator will only be blocking
for one response (the data response).
Cheers
Aaron
-
Aaron Morton
Yeah, but all the requests for data/digest are sent at the same time… responses
that aren’t “needed” to complete the request are dealt with asynchronously
(possibly causing repair).
In the original trace (which is confusing because I don’t think the clocks are
in sync)… I don’t see anything th
Perfect,
Thanks, that solved it.
Regards
Mark.
From: Aaron Morton [mailto:aa...@thelastpickle.com]
Sent: Monday, May 12, 2014 2:21 PM
To: Cassandra User
Subject: Re: Question about READS in a multi DC environment.
> read_repair_chance=1.00 AND
Theres y
> > read_repair_chance=1.00 AND
There’s your problem.
When read repair is active for a read request the coordinator will over read to
all UP replicas. Your client request will only block waiting for the one
request (the data request), the rest of the repair will happen in the
background.
Ins't read repair supposed to be done asynchronously in background ?
On Mon, May 12, 2014 at 2:07 AM, graham sanderson wrote:
> You have a read_repair_chance of 1.0 which is probably why your query is
> hitting all data centers.
>
> On May 11, 2014, at 3:44 PM, Mark Farnan wrote:
>
> > Im tryi
You have a read_repair_chance of 1.0 which is probably why your query is
hitting all data centers.
On May 11, 2014, at 3:44 PM, Mark Farnan wrote:
> Im trying to understand READ load in Cassandra across a multi-datacenter
> cluster. (Specifically why it seems to be hitting more than one DC)
Im trying to understand READ load in Cassandra across a multi-datacenter
cluster. (Specifically why it seems to be hitting more than one DC) and hope
someone can help.
From what Iím seeing here, a READ, with Consistency LOCAL_ONE, seems to be
hitting All 3 datacenters, rather than just the
