Thanks Sam - a couple of subtleties there that we missed in our review.
Cheers
Ben
On Tue, 30 Aug 2016 at 19:42 Sam Tunnicliffe wrote:
> Just to clarify a little further, it's true that read repair queries are
> performed at CL ALL, but this is slightly different to a regular,
> user-initiated
Just to clarify a little further, it's true that read repair queries are
performed at CL ALL, but this is slightly different to a regular,
user-initiated query at that CL.
Say you have RF=5 and you issue read at CL ALL, the coordinator will send
requests to all 5 replicas and block until it receiv
In case anyone else is interested - we figured this out. When C* decides it
need to do a repair based on a digest mismatch from the initial reads for
the consistency level it does actually try to do a read at CL=ALL in order
to get the most up to date data to use to repair.
This led to an interest
Looking at the wiki for the read path (
http://wiki.apache.org/cassandra/ReadPathForUsers), in the bottom diagram
for reading with a read repair, it states the following when "reading from
all replica nodes" after there is a hash mismatch:
If hashes do not match, do conflict resolution. First step