that makes sense. thanks!
On Apr 7, 2011, at 8:36 AM, Stephen Connolly wrote:
> also there is a configuration parameter that controls the probability of any
> read request triggering a read repair
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
also there is a configuration parameter that controls the probability of any
read request triggering a read repair
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 7 Apr 2011
as I understand, the read repair is a background task triggered by the read
request, but once the consistency requirement has been met you will be given
a response.
the coordinator at CL.ONE is allowed to return your responce once it has one
response (empty or not) from any replica. if the first r
Let's say you have RF of 3 and a write was written to 2 nodes. 1 was not
written because the node had a network hiccup (but came back online again).
My question is, if you are reading a key with a CL of ONE, and you happen to
land on that node that didn't get the write, will the read fail imm
