[SERVER-63648] Figure out if config and shard can share replica set name for the hybrid POC Created: 15/Feb/22  Updated: 12/Apr/22  Resolved: 12/Apr/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Witten (Inactive)
Resolution: Done Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-63598 Umbrella ticket for minimal POC for o... Closed
Duplicate
is duplicated by SERVER-63649 Investigate how to make the replicati... Closed
Sprint: Sharding 2022-02-21, Sharding 2022-03-07
Participants:

 Description   

I need to crack this separately, find out if Config server can share the same Replica Set name, or need to find the way to trick the replication layer into accepting two different replica set names for the shard and config server. Investigation ticket to do it cleanly is separate.

Alternatively, keep a single replica set name and find how far we can go on this path in POC.



 Comments   
Comment by Andrew Witten (Inactive) [ 12/Apr/22 ]

I currently don't see an issue with the catalog shard (hybrid shard) having a single replica set name.

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