[SERVER-76310] Use config shard terminology instead of catalog shard Created: 19/Apr/23  Updated: 29/Oct/23  Resolved: 24/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 7.1.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:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0
Sprint: Sharding NYC 2023-05-01
Participants:

 Description   

We've decided to use the term "config shard" for a config server that is acting as a shard eligible for user data. The development term was "catalog shard" and will need to be changed. We'll also update the transitionToCatalogShard command to be transitionFromDedicatedConfigServer.



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

Author:

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

Message: SERVER-76310 Use config shard terminology instead of catalog shard

(cherry picked from commit e3e4b4d6a54a671e564d8bd9e4b34188ab4accd0)
Branch: v7.0
https://github.com/mongodb/mongo/commit/7100c3e079dc6347949536300fd79cba421ed576

Comment by Githook User [ 24/Apr/23 ]

Author:

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

Message: SERVER-76310 Use config shard terminology instead of catalog shard
Branch: master
https://github.com/mongodb/mongo/commit/e3e4b4d6a54a671e564d8bd9e4b34188ab4accd0

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