-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-01-22
-
155
The goal of SERVER-60621 was to ban all Global Lock upgrades (which was essentially completed in --> SERVER-66145).
This ticket aims to ban all lock upgrades not just global lock upgrades. At this time, lock upgrades occur in LockManager::convert() and the motivation behind this ticket would be the same as in SERVER-60621 "as it could help us identify additional bugs we haven't hit yet, and avoid future ones".
- causes
-
SERVER-85232 Set `InMultiDocumentTransaction` flag when recovering committed distributed transactions
- Closed
- depends on
-
SERVER-72703 Downgrade $out's db lock to MODE_IX
- Closed
-
SERVER-60621 Investigate if we can ban upgrading the global lock
- Closed
-
SERVER-73043 Avoid upgrading lock in dbtests
- Closed
-
SERVER-73058 QueryStageCollectionScanTest acquires global IX lock and then calls AutoGetCollectionForRead
- Closed
-
SERVER-73101 Avoid upgrading locks in db unit tests
- Closed
-
SERVER-73249 Investigate behavior for requesting IS when IX is held
- Closed
-
SERVER-80428 Avoid lock upgrade when renaming collection for apply ops
- Closed
-
SERVER-80942 Prevent lock upgrade in createIndexes under transaction
- Closed
-
SERVER-80963 Prevent lock upgrade in ShardingRecoveryService::acquireRecoverableCriticalSectionBlockWrites when using config namespace
- Closed
-
SERVER-81051 Prevent lock upgrade when aborting index build on step up
- Closed
-
SERVER-84668 Avoid tenant lock upgrade when applying change collection creation oplog entry
- Closed
- is duplicated by
-
SERVER-73060 Remove lock upgrade tests in LockManagerTest
- Closed