[SERVER-79302] Support per-collection SetUserWriteBlockMode Created: 25/Jul/23  Updated: 23/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Craven Huynh Assignee: Matt Panton
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Assigned Teams:
Sharding EMEA
Backport Requested:
v7.3
Sprint: Sharding EMEA 2023-08-21
Participants:

 Description   

In order to allow a Mongosync migration to be reversible, the setUserWriteBlockMode command was added to MongoDB.

As part on the Mongosync many-to-one epic REP-1989, users will be allowed to perform multiple migrations from multiple source clusters into a single destination cluster at the same time, as long as each migration's collections are mutually exclusive.

In order to allow individual migrations to be reversible, we will need to enable UserWriteBlockMode on the subset of collections on the destination that are not included in the reverse-migration or disable UserWriteBlockMode on the subset of collections on the destination that are included in the reverse-migration.

 

Ideally, the enableUserWriteBlockMode and disableUserWriteBlockMode commands will be added. They would take a list of namespaces "databaseName.collectionName" that we want to either enable or disable userWriteBlockMode on. Running the enable command on a namespace that already has userWriteBlockMode enabled should not do anything, likewise for the disable command.

The list of namespaces could include both sharded and unsharded namespaces.


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