[SERVER-60336] Remove the MigrationScheduler component from the Balancer (and replace it with BalancerCommandsScheduler) Created: 30/Sep/21  Updated: 29/Oct/23  Resolved: 26/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-61113 _configsvrMoveChunk does not gossip t... Closed
Related
related to SERVER-59691 Coverity analysis defect 120619: Pars... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-10-18, Sharding EMEA 2021-11-01
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 26/Oct/21 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-60336 Replace the balancer's MigrationScheduler with a BalancerCommandsScheduler
Branch: master
https://github.com/mongodb/mongo/commit/4a8881d3f61be8e57b55a33e076bace92b3e6aad

Generated at Thu Feb 08 05:49:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.