Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
v4.4
-
Repl 2020-03-23
-
50
Description
In kLogOp mode, AutoGetOplog only acquires collection lock for non-document-locking storage engines if it is not already held. However, AutoGetOplog uses ShouldNotConflictWithSecondaryBatchApplicationBlock which makes isCollectionLockedForMode always return true, resulting in skipping collection lock for kLogOp mode under non-document-locking storage engines.
Attachments
Issue Links
- related to
-
SERVER-45626 Consistent Oplog Locking Rules
-
- Closed
-