[SERVER-82408] Deprecate ConfigsvrSetAllowMigration command Created: 24/Oct/23  Updated: 31/Oct/23

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

Type: Task Priority: Minor - P4
Reporter: Marcos José Grillo Ramirez Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-82592 Remove _kChunkOpLock lock Backlog
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2023-10-30
Participants:

 Description   

Currently for sharded clusters collmod, drop collection, drop database, refine collection shard key and rename uses the ConfigsvrSetAllowMigration command to leave the cluster in a steady state regarding migrations before doing any metadata change.

The command was done in SERVER-53861 in a time where PM-2210 was not implemented so it was not possible running cluster wide transactions internally. We can now deprecate the ConfigsvrSetAllowMigrations command and move it's implementation to every DDL coordinator using a remote transaction with the internal API.


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