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

move_chunk_allowMigrations 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-04-15
    • 28
    • 1

      SERVER-87613 removed the shard versioning check from move_chunk_permitMigrations but there are similar checks in move_chunk_allowMigrations. These checks assume that the filtering information is known after a shardCollection command completes, which is not neccessarily true. They should either be removed since they are checking internal workings of the shard versioning protocol or a command should be run via the mongoS prior to the checks to ensure that the filtering information has been recovered.

            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: