[SERVER-70924] Create collection should disable migrations until successfully commit Created: 28/Oct/22  Updated: 02/Feb/23  Resolved: 25/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Enrico Golfieri Assignee: Pol Pinol
Resolution: Won't Fix Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
Participants:
Story Points: 3

 Description   

after SERVER-70167 a quick fix prevents the invariant from crashing the server due to a possible migrations acquiring the critical sections after a failure.

However, a better approach would be:

  • disable migrations when create collection starts
  • resume migrations when create collection commits

 



 Comments   
Comment by Pol Pinol [ 25/Jan/23 ]

Closing this ticket as won't fix because checking if the collection has migrations allowed, it is not a consistent proof that after that, migrations are still paused / resumed.

Generated at Thu Feb 08 06:17:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.