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

RangeFetchMapCalculator should not try to optimise 'trivial' ranges

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

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 4.0-alpha1, 4.0
    • None
    • None
    • Normal

    Description

      RangeFetchMapCalculator (CASSANDRA-4650) tries to make the number of streams out of each node as even as possible.

      In a typical multi-dc ring the nodes in the dcs are setup using token + 1, creating many tiny ranges. If we only try to optimise over the number of streams, it is likely that the amount of data streamed out of each node is unbalanced.

      We should ignore those trivial ranges and only optimise the big ones, then share the tiny ones over the nodes.

      Attachments

        Activity

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

          People

            marcuse Marcus Eriksson Assign to me
            marcuse Marcus Eriksson
            Marcus Eriksson
            Ariel Weisberg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment