> I have following understanding about Cassandra read repair: Read Repair is an automatic process that reads from more nodes than necessary during a normal read and checks and repairs differences in the background. It’s different to “repair” or Anti Entropy that you run with nodetool repair.
> • If we write with QUORUM and read with QUORUM then we do not need to > externally (nodetool) trigger read repair. You normally still want to run repair because it’s the way to ensure Tombstones are distributed. > • Since we are reading + writing with QUORUM then it is safe to set > "read_repair_chance=0 & dclocal_read_repair_chance=0" in column family > definition. It’s safe, read repair does not affect consistency. It’s designed to reduce the chance that the server will need to repair an inconsistency during a read for a client. Cheers ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 12/01/2014, at 11:31 am, chovatia jaydeep <chovatia_jayd...@yahoo.co.in> wrote: > Hi, > > I have following understanding about Cassandra read repair: > • If we write with QUORUM and read with QUORUM then we do not need to > externally (nodetool) trigger read repair. > • Since we are reading + writing with QUORUM then it is safe to set > "read_repair_chance=0 & dclocal_read_repair_chance=0" in column family > definition. > Can someone please clarify? > > -jaydeep
