-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2024-03-18, CAR Team 2024-04-01
Today, a MongoD node can act as a router. This implies that MongoD should be able to run same functionalities as a MongoS does. There are some calls in the codebase that checks for ClusterRole::RouterServer in an exclusive mode, without considering that MongoD can act as a router and shard. That is, some of those calls may be outdated.
Goal
We need to revisit each exclusive check for ClusterRole::RouterServer in serverGlobalParams.clusterRole to ensure that a MongoD acting as a router has the same behavior as a standalone MongoS.
References
Estimation
- User impact: Routing logic of MongoD may hit some invariant or assertion.
- Raw estimation: 5 man-days
- is related to
-
SERVER-88270 Investigate analyze shard key code when checks serverGlobalParams.clusterRole for RouterServer in exclusive mode
- Backlog
-
SERVER-87691 Remove explicit serverGlobalParams.clusterRole check from state change error rewrite library
- Closed