[SERVER-75096] Locally drop sharded collections from config server during transitionToDedicatedConfigServer Created: 21/Mar/23  Updated: 29/Oct/23  Resolved: 03/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-75646 Wait for range deletions before dropp... Closed
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-04-03, Sharding NYC 2023-04-17
Participants:

 Description   

Before completing the transition from catalog shard mode to dedicated mode, all sharded collections that exist on the config server locally should be dropped locally. This is to prevent their collection options and indexes from getting out of sync, since collMod, createIndexes, etc. won’t target a dedicated config server. If the config server transitions back to catalog shard mode, it will copy the necessary options/indexes when receiving the first chunk for a collection.

EDIT: We can't add a the config server as a shard if it has a local database that conflicts with a database in the cluster, so this isn't necessary for correctness, but it does let a user add the config server as a shard after removing it without manually dropping its empty local collections.



 Comments   
Comment by Githook User [ 03/Apr/23 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-75096 Locally drop sharded collections in transitionToDedicatedConfigServer
Branch: master
https://github.com/mongodb/mongo/commit/96ea1942d25bfc6b2ab30779590f1b8a8c6887b5

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