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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.10, 4.0.4, 4.1.5
    • Affects Version/s: 4.0.2, 4.1.3
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • 4

      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.

            james.wahlin@mongodb.com James Wahlin
            james.wahlin@mongodb.com James Wahlin
            0 Vote for this issue
            3 Start watching this issue