Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-930

make RR chance configurable

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 0.7 beta 1
    • Component/s: None
    • Labels:
      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.

        Attachments

          Activity

            People

            • Assignee:
              mdennis Matthew F. Dennis Assign to me
              Reporter:
              jbellis Jonathan Ellis
              Authors:
              Matthew F. Dennis

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment