[SERVER-61760] The new implementation of CollMod should rely on the AllowMigrations to stop/resume migrations Created: 29/Nov/21  Updated: 29/Oct/23  Resolved: 17/Jan/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-62746 resharding_prohibited_commands.js fai... Closed
causes SERVER-70321 Collmod coordinator must not resume m... Closed
Backwards Compatibility: Fully Compatible
Sprint: 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
Participants:
Linked BF Score: 161

 Description   

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).



 Comments   
Comment by Githook User [ 17/Jan/22 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-61760 Stop migrations in sharded collections before executing a collMod command
Branch: master
https://github.com/mongodb/mongo/commit/59d341f677f355939c6f4e8e9934ea1de700c1f7

Comment by Marcos José Grillo Ramirez [ 13/Dec/21 ]

The original work for SERVER-6094 was reverted because of the 5.2 branching, so, once the work is recommitted, I'll continue with this task.

Generated at Thu Feb 08 05:53:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.