[SERVER-72818] Wait for range deleter service to be fully initialized before transitioning to primary Created: 13/Jan/23  Updated: 29/Oct/23  Resolved: 17/Jan/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 6.2.0-rc6
Fix Version/s: 6.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
is caused by SERVER-68348 Asynchronously register tasks on the ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.2
Sprint: Sharding EMEA 2023-01-23
Participants:
Linked BF Score: 0

 Description   

On step up complete, the range deleter service is asynchronously spawning the recovery of existing range deletions before setting its state as "up".

Since the scheduling of new range deletions is disallowed while the service is not up, this may lead to errors in case a very fast migration commits (or simply when an already committed migration gets recovered).

A possible solution to overcome this problem would be to spawn range deletion recovery when step-up begins and waiting for the component to be up before transitioning to primary.



 Comments   
Comment by Githook User [ 17/Jan/23 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-72818 Wait for range deleter service to be fully initialized before transitioning to primary
Branch: master
https://github.com/mongodb/mongo/commit/508af5348d4f7add4584b56ebc171ab645a49f34

Generated at Thu Feb 08 06:22:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.