Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-16278

Investigate changes in SERVER-77917: MongoD opens a second listening port dedicated to routing requests

      Original Downstream Change Summary

      Introduces a new listening port for `mongod` servers, to listen for connections from other shard-servers when `mongod` acts as both shard-server and router. This is currently guarded behind a feature-flag.

      Description of Linked Ticket

      The MongoD process should open a second listening port to receive requests which will be routed (by the embedded router) to the proper shards.

      The characteristics of this port should be the same of the one opened by the MongoS (i.e., default port number, limit on the connections, etc.). The MongoD executable should accept the expected arguments to customize that port behaviour.

      As a consequence, operation contexts and clients should have a getter function to determine the origin of the request, i.e., from router or shard port.

      On the other hand, the standalone router (i.e., MongoS) should mark operation contexts and clients accordingly (from router by default).

            Assignee:
            jocelyn.mendez@mongodb.com Jocelyn Mendez
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              39 weeks, 4 days ago