-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Execution Team 2025-02-17, Storage Execution 2025-03-03
As part of SERVER-99150 we've implemented a lock ordering checker across the database. It detected a lock ordering conflict with the commit quorum lock used in the class and the RSTL lock.
The class has the following two lock orderings:
- Lock the commitQuorum mutex -> Lock the index build entry collection which happens to lock the RSTL
- Lock the RSTL lock -> Lock the commit quorum lock
As the commit quorum lock is exclusively locked and the RSTL lock is used during stepdown there might be a lock ordering conflict at play here that we haven't yet triggered. We should investigate if there's an actual issue and attempt to fix it if needed.
- related to
-
SERVER-99150 Make threads always acquire locks with strict ordering
-
- Closed
-