[SERVER-76998] The commit setAllowMigrations command do work that should be done in the DDL coordinators Created: 10/May/23  Updated: 26/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:

 Description   

Currently, when committing a change to the allowMigrations flag, after executing a transaction to change the collection metadata and bump one chunk, there is a refresh sent to all shards. This is done to make all the shards aware of the change, and abort any ongoing migration if necessary.

This is correct, but it applies the pull model, which we're trying to move out from. We should instead, leave the commit command to simply change the collection metadata, and then make coordinators trigger the refresh if necessary.


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