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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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 José Grillo Ramirez
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: