[SERVER-60827] File Copy Based Initial Sync needs to keep opCtx, client, and thread coherent. Created: 19/Oct/21  Updated: 29/Oct/23  Resolved: 21/Oct/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: Repl 2021-11-01
Participants:

 Description   

We need to hold the global lock across scheduled calls in FileCopyBasedInitialSyncer. Our current method for doing this involves holding RAII objects (GlobalLock) in places other than the stack. GlobalLock holds an _opCtx, and _opCtx are associated with a particular client, which are typically associated with a particular thread. We need to use a different method to keep this lock held.



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

Author:

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

Message: SERVER-60827 File Copy Based Initial Syncer: Fix global locking.

Keep opCtx with global lock, associated client, and current thread all in sync.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/829d0a02f494620126080cd6352d82de5ff86751

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