-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2022-06-13
Investigation to ban global lock upgrades is ongoing in SERVER-60621. While working on dependent SERVER-61788, avoid the lock upgrade in StorageTimestampTest.SecondaryInsertTimes, we have found that MultiDocumentTransactionTest also fails due to a global lock upgrade from MODE_IS to MODE_IX in the constructor of MongoDOperationContextSession.
This issue does not appear to be with the test itself, but something general.
Attached backtrace.log.
Comment from Dan Larkin-York.
- depends on
-
SERVER-61733 Determine if global lock upgrade is necessary in transaction_participant.cpp:fetchActiveTransactionHistory
- Closed
- is depended on by
-
SERVER-60621 Investigate if we can ban upgrading the global lock
- Closed
- is related to
-
SERVER-61788 Determine if we can avoid global lock upgrade in dbtest StorageTimestampTest
- Closed