WiredTigerRecordStore::reclaimOplog can block for extended periods of time

XMLWordPrintableJSON

    • 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: