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

move_chunk_permitMigrations should not assume the shard's filtering metadata is correct after shardCollection

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-03-18
    • 28

      In move_chunk_permitMigrations.js, we are sharding a collection and then checking that the collection version on the shard is a certain value. However, there are no guarantees that the shard knows its filtering information when shardCollection finishes. SERVER-80135 additionally made it more likely that the shard doesn't know its filtering information when the operation finishes, causing this test to fail.

      The test should perform some operation against the collection in order to ensure that the shard knows the correct filtering information or simply remove the check of the shard version on the shard.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: