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

Repair improvements when using vnodes

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
    • Normal
    • Resolution: Fixed
    • 3.0 beta 1
    • None

    Description

      Currently when using vnodes, repair takes much longer to complete than without them. This appears at least in part because it's using a session per range and processing them sequentially. This generates a lot of log spam with vnodes, and while being gentler and lighter on hard disk deployments, ssd-based deployments would often prefer that repair be as fast as possible.

      Attachments

        1. cassandra-3.0-5220-2.patch
          89 kB
          Marcus Olsson
        2. cassandra-3.0-5220-1.patch
          94 kB
          Marcus Olsson
        3. cassandra-3.0-5220.patch
          64 kB
          Marcus Olsson
        4. 5220-yourkit.tar.bz2
          2.18 MB
          Ryan McGuire
        5. 5220-yourkit.png
          32 kB
          Ryan McGuire

        Issue Links

        Activity

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

          People

            molsson Marcus Olsson Assign to me
            brandon.williams Brandon Williams
            Marcus Olsson
            Stefania Alborghetti
            Votes:
            14 Vote for this issue
            Watchers:
            46 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment