[SERVER-45059] currentOp's waitingForLatch field is misleading Created: 11/Dec/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Participants:
Case:

 Description   

Currently, if any Client thread is blocked in a call to waitForConditionOrInterrupt, it will show up in the currentOp output as both "active:true" and with a "waitingForLatch" field identifying the Mutex associated with the condition variable being waited on. This output suggests the Mutex (Latch?) is locked and that the code is blocked waiting to acquire it, but this is a false suggestion.


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