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

IndexBuildTest.getIndexBuildOpId() not selective enough when IndexBuildsCoordinator is enabled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1, 4.2.4
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Execution Team 2019-07-01, Execution Team 2019-07-15
    • Linked BF Score:
      5

      Description

      When the primary is building the index with the IndexBuildsCoordinator, there could be two db.currentOp() entries for the index build: one for the command invocation on the client connection and another for the task in the thread pool managed by the IndexBuildsCoordinator. The operation performing the actual work should be the one with a non-empty 'locks' field and should be preferred over the client connection operation.

      This affects mostly JS tests that attempt to locate and modify the state of an active index build when the enableIndexBuildsCoordinatorForCreateIndexesCommand server parameter is enabled.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              benety.goh Benety Goh
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: