[SERVER-63161] The recovery of the shard version and the migration in the moveChunk should be done in a separate thread Created: 01/Feb/22  Updated: 29/Oct/23  Resolved: 07/Feb/22

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Related
is related to SERVER-63314 Remove unused fail points in migratio... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Participants:
Linked BF Score: 137

 Description   

SERVER-62282 added a recovery of the shard version and migrations until it suceeds. The problem is that we are running it on the same thread that was executing the different phases of the moveChunk on the donor. This could produce a deadlock, which is very well described in BF-24170.



 Comments   
Comment by Githook User [ 07/Feb/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-63161 The recovery of the shard version and the migration in the moveChunk should be done in a separate thread
Branch: master
https://github.com/mongodb/mongo/commit/111c63d91c067b00199635c42243d43784e7145b

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