-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding 2022-02-21, Sharding 2022-03-07
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is depended on by
-
SERVER-63598 Umbrella ticket for minimal POC for optional config server
-
- Closed
-
- is duplicated by
-
SERVER-63649 Investigate how to make the replication layer to handle replica set name[s] for shard and config
-
- Closed
-