Remove the MigrationScheduler component from the Balancer (and replace it with BalancerCommandsScheduler)

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2021-10-18, Sharding EMEA 2021-11-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The Balancer is currently relying on the MigrationManager for

      1. submitting automated and manual moveChunk commands to the target shards
      2. rejoining ongoing migrations when a new Config Server Primary steps up / recovers from a crash.

      Such logic is duplicated within BalancerCommandsScheduler, which has been developed to support the execution of the Routing table defragmentation algorithm.

      The team analysed the redundancy and believes that it can be consolidated in a single component.

              Assignee:
              Paolo Polato
              Reporter:
              Paolo Polato
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: