[SERVER-61377] Fix File Copy Based Initial Sync shutdown and config races Created: 10/Nov/21  Updated: 29/Oct/23  Resolved: 18/Nov/21

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

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Replication 2021-11-15, Replication 2021-11-29
Participants:

 Description   

The File Copy Based Initial Syncer may be shut down via signal during a storage change. This results in a deadlock because the storage change cannot complete until the shutdown opCtx is destroyed, which it never will be. Fixed by doing initial syncer shutdown slightly earlier, before the shutdown opCtx is created.

Additionally there is a race between config changes and storage change which can cause an invariant.



 Comments   
Comment by Githook User [ 12/Nov/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-61377 Fix File Copy Based Initial Sync shutdown and config races

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