-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.3, 3.6.3
-
Component/s: Replication, Storage
-
None
-
Storage Execution
-
ALL
-
Execution Team 2019-09-09
In the case where we're truncating a very large amount of oplog entries, WiredTigerRecordStore::reclaimOplog may hold its locks (Global IX since 3.6, DB/Collection IX for the oplog in 3.4) for an extended period of time, blocking operations such as stepdown which may require a global X lock.
One potential solution to this problem is for reclaimOplog to yield all locks periodically.
- is related to
-
SERVER-30727 Secondary stuck in loop of current election
- Closed
-
SERVER-43322 Add tracking tools for measuring OplogStones performance
- Closed
-
WT-4011 Checkpoint should not read truncated pages
- Closed
-
SERVER-34129 Don't hold database or collection locks during oplog truncation
- Closed