Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
None
-
None
Description
Read load increases linearly with replication factor. While this can be mitigated by simply adding machines, it would also be nice to be able to configure on a per-CF basis the chance of performing a read repair, so that particularly heavily read CFs could have a chance of (say) 10% and seldom-used ones could continue to repair every time, i.e., chance of 100%. Thus, the "hot keys get repaired before waiting for anti-entropy to kick in" property gets preserved, but you might see a few more reads serving old values than before.