Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-75435

Investigate scope of _oplogPinnedByBackupMutex in WiredTigerKVEngine::beginNonBlockingBackupCursor()

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution
    • Execution Team 2023-05-01, Execution Team 2023-05-15

    Description

      The _oplogPinnedByBackupMutex is locked and held for the majority of WiredTigerKVEngine::beginNonBlockingBackup()

      The mutex is locked before the trying to acquire the PBWM lock. We've seen scenarios where minor changes to the oplog applier code path can introduce a deadlock where the oplog applier holds the PBWM lock while trying to check the oldest pinned timestamp.

      In general, we should try to limit the scope of this mutex, and evaluate if the scope can be reduced to improve code safety.

      Attachments

        Activity

          People

            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: