[SERVER-64987] Add support for concurrent DDL operations on the same database Created: 28/Mar/22  Updated: 06/Jul/23  Resolved: 06/Jul/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-61759 Unsetting the AllowMigrations flag sh... Closed
Duplicate
duplicates SERVER-77422 Change DDL lock mode acquisitions Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Currently we use the DistLock manager to syncronize DDL operations.

Historically DistLocks was required for DDL operations to syncronize with ongoing migrations.

After SERVER-61759 it is not necessary anymore to use DistLock on DDL operations since they all use sharding_ddl_util::stopMigrations to drain and serialize with migrations on a specific collections.

This means that once 6.0 became last LTS we can make DDL operations to start using a node-local-only synchronization mechanism. Moreover by using a local syncronization mechanism that support shared/exclusive mode we will be able to support concurrent DDL operations for the same database.



 Comments   
Comment by Silvia Surroca [ 06/Jul/23 ]

This feature has already been addressed by PM-2850

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