[DOCS-16278] Investigate changes in SERVER-77917: MongoD opens a second listening port dedicated to routing requests Created: 25/Jul/23  Updated: 13/Nov/23  Resolved: 20/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Jocelyn Mendez
Resolution: Fixed Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-77917 (SA) MongoD opens a second listening ... Closed
Participants:
Days since reply: 28 weeks, 1 day ago

 Description   
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).


Generated at Thu Feb 08 08:15:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.