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

The new implementation of CollMod should rely on the AllowMigrations to stop/resume migrations

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24
    • 161

      Right now we are relying on the DistLock objects to guarantee that CollMod is not executed concurrently with a migration over the same collection.  However DistLock objects will be removed soon, so instead of relying on them we should call to stopMigrations from the CollMod coordinator + add a new method to resumeMigrations (it should be a very similar code).

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: