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

blacklist validate_db_metadata_command.js from migrations suite

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.1, 7.3.0-rc0, 7.0.5
    • Affects Version/s: 6.3.0, 7.0.0, 7.1.0, 7.3.0-rc0, 7.2.0-rc3
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v7.2, v7.0
    • Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27
    • 3

      The test performs the following operation

      • create an invalid index
      • drop the invalid index
      • run validateDbMetadata and check no errors are returned

      However, due to migrations the following might happen:

      • Drop starts
      • Migration from shard0 to shard1 starts
      • Migration starts creation of index on shard1
      • Drop index drops on shard0 but not shard1 (not committed yet)
      • Migration now commits the create index on shard1

      in this case, we have left an invalid index on shard1, which will make the test failing. The test should stay black-listed until PM-2077 is completed which should solve the known issue.

            Assignee:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Reporter:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: