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

list_indexes_with_build_uuids.js - IndexBuildTest.assertIndexes() sees different server state from IndexBuildTest.getIndexBuildOpId()

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.9.0
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-11-02
    • 23

    Description

      The listIndexes command in list_indexes_with_build_uuids.js is run on the secondary after checking the db.currentOp() output. However, this command may read the catalog state before the secondary has completed applying the batch of oplog entries containing the startIndexBuild command. This will lead to the test not detecting the in-progress index build.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-51703 index_secondary_wait_for_commit.js - IndexBuildTest.assertIndexes() sees different server state from IndexBuildTest.getIndexBuildOpId()

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-51792 index_failover_key_errors.js and indexbg_killop_stepup.js can check indexes before the abort timestamp is reached

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: