[SERVER-54885] Ensure add/remove shards work with DDL operations on fsm workload Created: 02/Mar/21  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   

There might be some scenarios where the add/remove shard while executing a DDL operation will cause failures or unexpected behaviors on the commands, we should check and fix them and remove the tag so the workload can be run on the add/remove shard suite. It is not intended to find a proper solution, that will be done on PM-2050, just to ensure that the DDL operation do not fail when trying to send a command to a removed shard.



 Comments   
Comment by Kaloian Manassiev [ 22/Apr/21 ]

The scope of this ticket is:
#. Theoretically convince ourselves that add/removeShard and concurrent DDL should work: It should, because in order to remove a shard, we need to move all chunks and primaries from there. Since moveChunk/Primary are blocked by DDL, this should not be possible.
#. Make sure that the broadcast against all shards done by certain coordinators is resilient to one of the shards disappearing due to removeShard (this will be addressed by SERVER-55150)
#. Enable the DDL + CRUD FSM workloads with add/removeShard and see what falls-out

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