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

make RR chance configurable

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 0.7 beta 1
    • 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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mdennis Matthew F. Dennis Assign to me
            jbellis Jonathan Ellis
            Matthew F. Dennis
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment