-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
ALL
-
Repl 2019-06-17
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.
- duplicates
-
SERVER-41009 TimestampMonitor and getOldestActiveTimestamp shouldn't conflict with PBWM lock
- Closed