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).
- causes
-
SERVER-62746 resharding_prohibited_commands.js fails due to allowMigrations being unexpectedly true from collMod command continuing to run
- Closed
-
SERVER-70321 Collmod coordinator must not resume migrations on retriable errors
- Closed