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

retrieving storage stats for currentOp blocked by slow oplog application

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1, 4.2.14
    • None
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Execution Team 2020-01-13
    • 20

    Description

      On a secondary node, the currentOp command includes storage stats in its slow op log. If oplog application is taking too long to apply a batch of operations, this may prevent the currentOp from completing in a timely manner.

      =========

      The defect addressed here primarily involves the Parallel Batch Writer Mutex (PBWM), a logical resource that is required for oplog application on a secondary node. Prior to this fix, it was possible for the database profiler and the currentOp command to compete for the PBWM resource with secondary oplog application.

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: