Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
ALL
-
Repl 2019-06-17
Description
The OplogTruncaterThread acquires a global IX lock here. This calls WiredTigerRecordStore::reclaimOplog(), which calls WiredTigerKVEngine::getPinnedOplog(), which calls WiredTigerKVEngine::getOplogNeededForRollback(), which calls TransactionParticipant::getOldestActiveTimestamp(), which acquires a global IS lock in a different locker here. This can self-deadlock if there is a pending strong lock acquisition.
Attachments
Issue Links
- duplicates
-
SERVER-41009 TimestampMonitor and getOldestActiveTimestamp shouldn't conflict with PBWM lock
-
- Closed
-