[SERVER-69406] Place InterruptibleLockGuards in the find and aggregation command paths Created: 02/Sep/22  Updated: 29/Oct/23  Resolved: 08/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-67424 Seek and destroy open storage cursors... Open
related to SERVER-69059 Create an InterruptibleLockGuard to p... Closed
is related to SERVER-69506 An InterruptibleLockGuard should be p... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-09-19
Participants:

 Description   

We need to ensure that yielding during find/agg cmds cannot hang during lock acquisition.



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

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-69406 Place an InterruptibleLockGuard in the find cmd path because it runs without a ClientCursorPin
Branch: master
https://github.com/mongodb/mongo/commit/fbd396a5acef49a31a235cdb2ce1e1f76c04a70a

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