[SERVER-48702] Latch order violation Created: 10/Jun/20  Updated: 06/Dec/22  Resolved: 17/Nov/20

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Backlog - Service Architecture
Resolution: Won't Fix Votes: 0
Labels: servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Service Arch
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

[ShardedClusterFixture:job3:shard0:secondary0] | 2020-04-25T00:20:54.240+00:00 I  -        23162   [conn40] "Dumping Latch Identities","attr":{"names":["RemoteCommandRetryScheduler::_mutex"]}
[ShardedClusterFixture:job3:shard0:secondary0] | 2020-04-25T00:20:54.240+00:00 F  -        23093   [conn40] "Fatal assertion","attr":
{
  msgid: 31360,
  error: "HierarchicalAcquisitionLevelViolation: Theoretical deadlock alert - InvalidWasAbsent latch acquisition at src/mongo/executor/network_interface_tl.cpp:113 on latch NetworkInterfaceTL::_mutex",
  file: "src/mongo/util/latch_analyzer.cpp",
  line: 231
}


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