;
>
> Original message ----
> Subject: Re: Read during digest mismatch
> From: Edward Capriolo
> To: "user@cassandra.apache.org"
> CC:
>
>
> I think the code base does not benefit from having too many different read
> code paths. Logically wha
From my understanding, if CL = 2, one read, one digest are sent. Only if it
is read repair, digest is sent to all replicates.
Thanks.
-Wei
Sent from my Samsung smartphone on AT&T
Original message
Subject: Re: Read during digest mismatch
From: Edward Capriolo
I think the code base does not benefit from having too many different read
code paths. Logically what your suggesting is reasonable, but you have to
consider the case of one being slow to respond.
Then what?
On Tuesday, November 13, 2012, Manu Zhang wrote:
> If consistency is two, don't we just
If consistency is two, don't we just send data request to one and digest
request to another?
On Mon, Nov 12, 2012 at 2:49 AM, Jonathan Ellis wrote:
> Correct. Which is one reason there is a separate setting for
> cross-datacenter read repair, by the way.
>
> On Thu, Nov 8, 2012 at 4:43 PM, san
Correct. Which is one reason there is a separate setting for
cross-datacenter read repair, by the way.
On Thu, Nov 8, 2012 at 4:43 PM, sankalp kohli wrote:
> Hi,
> Lets say I am reading with consistency TWO and my replication is 3. The
> read is eligible for global read repair. It will send
Hi,
Lets say I am reading with consistency TWO and my replication is 3. The
read is eligible for global read repair. It will send a request to get data
from one node and a digest request to two.
If there is a digest mismatch, what I am reading from the code looks like
it will get the data from
