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

plan_cache_index_create.js should wait for index build start, rather than just createIndexes command start

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.0.2, 4.1.3
    • Fix Version/s: 3.6.10, 4.0.4, 4.1.5
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6
    • Linked BF Score:
      4

      Description

      The plan_cache_index_create.js test checks currentOp to confirm that an index build is running. Once confirmed it assumes that the createIndexes command has cleared the plan cache. This is an incorrect assumption to make as the createIndexes command will be visible in currentOp on command execution, which is prior to the MultiIndexBlock::init() call which triggers a clearQueryCache() call further down the call stack.

      Instead, we should confirm that the hangAfterStartingIndexBuild has been reached. Note that this change may not work for the calls to !indexBuildIsRunning() in this test, which can continue to use currentOp.

        Attachments

          Activity

            People

            Assignee:
            james.wahlin James Wahlin
            Reporter:
            james.wahlin James Wahlin
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: