-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
None
-
3
-
TBD
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
-
0
This leads to a shard where only the primary has sharding enabled, which can lead to all sorts of weird behavior if that node steps up to primary. Additionally, direct connection checks against the nodes without sharding enabled will not correctly be disallowed once a second shard is added to the cluster.