[SERVER-73865] Use config shard name for the config server Created: 09/Feb/23  Updated: 29/Oct/23  Resolved: 23/Feb/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

Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Participants:

 Description   

After SERVER-72489, the config server will always have a shardIdentity document. Initially it will use a fixed name of "catalogShard" but to simplify our system, it should use the "config" name, which is already used as the config server's shard id in places that require one, like two phase commit coordination and as the primary shard for the config and admin dbs.

There is also logic that special cases the config id to avoid failures from the config server not previously behaving like a normal shard, like not sending shard versions to it. The config server will now have all shard components, so we can remove those special cases, which is necessary to use "config" as the catalog shard's id.



 Comments   
Comment by Githook User [ 23/Feb/23 ]

Author:

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

Message: SERVER-73865 Use config shard name for the config server
Branch: master
https://github.com/mongodb/mongo/commit/09fe46995dca6375632632f5fc334035359db870

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