title: Reparing inconsistency when read_repair_chance = 0
body: <p>What I understand is that read_repair_chance is a probabilistic chance to trigger a ReadRepair over all the replicas. If an inconsistency is found the most recent update would serve to repair the data.</p>
  
  <p>ReadRepairs are too expensive for me because most of my read CL is ONE.
  So I choose read_repair_chance = 0 and dclocal_read_repair_chance = 0 too.</p>
  
  <p>But sometimes I use QUORUM instead of ONE. Read QUORUM is reached when two replicas respond, but the two records can be different. Cassandra return the one with the most recent timestamp. Does it try to repair the other one ?</p>