[SERVER-60922] Use `config.migrations` to persist the command recovery documents generated by BalancerCommandsScheduler. Created: 22/Oct/21  Updated: 29/Oct/23  Resolved: 07/Dec/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: Backlog
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:
Related
related to SERVER-47003 MaxTimeMSExceeded on _configsvrMoveCh... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13
Participants:

 Description   

BalancerCommandsScheduler is currently storing in config.balancerCommandsSchedulerOngoingOperations the information on commands to be re-issued after a step-down event (similarly to what the MigrationManager did with config.migrations, but using a different schema).

This may lead to some issues, such as:

  • outstanding moveChunk commands stored in config.migrations that won't be recovered after a server upgrade
  • outstanding moveChunk commands stored in config.balancerCommandsSchedulerOngoingOperations that won't be recovered after a server downgrade
  • stale moveChunk being wrongly re-issued after a downgrade+upgrade cycle.

The simplest way to solve this problem is to avoid interactions with the FCV routine - and to just keep using `config.migrations` for the task.



 Comments   
Comment by Githook User [ 07/Dec/21 ]

Author:

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

Message: SERVER-60922 Use config.migrations to persist moveChunk recovery info
Branch: master
https://github.com/mongodb/mongo/commit/d69f240a64dea20ca163a93b6eeb6494ea1e4a24

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