Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-87465

Revisit all calls that checks serverGlobalParams.clusterRole for RouterServer in exclusive mode

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 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

            Assignee:
            Unassigned Unassigned
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: