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

Fix and modernize currentop.js

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.12, 3.4.2, 3.5.1
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Fully Compatible
    • v3.4, v3.2
    • Query 2016-11-21, Query 2016-12-12
    • 0

      The test doesn't properly wait for the operations to be running when using the mmapv1 storage engine. It looks for operations to report holding or waiting for the "w" or "r" collection locks, which represent intent locks. This won't happen on mmapv1. Instead, the operations will report holding or waiting for the "W" or "R" collection locks respectively (the non-intent versions of these locks, which are not compatible with each other).

      While fixing the test, we should clean up the numerous unnecessary print statements, single letter variable names, etc. which make the test difficult to read and diagnose.

            charlie.swanson@mongodb.com Charlie Swanson
            charlie.swanson@mongodb.com Charlie Swanson
            0 Vote for this issue
            3 Start watching this issue