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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1, 4.2.4
    • None
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Execution Team 2019-07-01, Execution Team 2019-07-15
    • 20

    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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: