Re: read repair across DC and latency

2014-11-21 Thread Tyler Hobbs
On Wed, Nov 19, 2014 at 4:51 PM, Jimmy Lin y2klyf+w...@gmail.com wrote: # When you said send read digest request to the rest of the replica, do you mean all replica(s) in current and other DC? or just the one last replica in my current DC and one of the co-ordinate node in other DC? (our

Re: read repair across DC and latency

2014-11-19 Thread Jimmy Lin
Tyler, thanks for the detail explanation. Still have few questions in my mind # When you said send read digest request to the rest of the replica, do you mean all replica(s) in current and other DC? or just the one last replica in my current DC and one of the co-ordinate node in other DC?

Re: read repair across DC and latency

2014-11-18 Thread Tyler Hobbs
On Sun, Nov 16, 2014 at 5:13 PM, Jimmy Lin y2klyf+w...@gmail.com wrote: I have read that read repair suppose to be running as background, but does the co-ordinator node need to wait for the response(along with other normal read tasks) before return the entire result back to the caller? For

read repair across DC and latency

2014-11-16 Thread Jimmy Lin
I have a CF that use the default, read_repair_chance (0.1) and dc_read_repair_chance(0). Our read and write is all local_quorum, on one of the 2 DC, replication of 3. so a read will have 10% chance trigger a read repair to other DC. # I have read that read repair suppose to be running as