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

The commit setAllowMigrations command do work that should be done in the DDL coordinators

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing

      Currently, when committing a change to the allowMigrations flag, after executing a transaction to change the collection metadata and bump one chunk, there is a refresh sent to all shards. This is done to make all the shards aware of the change, and abort any ongoing migration if necessary.

      This is correct, but it applies the pull model, which we're trying to move out from. We should instead, leave the commit command to simply change the collection metadata, and then make coordinators trigger the refresh if necessary.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: