[DOCS-16233] Investigate changes in SERVER-78384: mongos should allow --port 0 Created: 30/Jun/23  Updated: 13/Nov/23  Resolved: 16/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 5.0.22, 7.0.3, 6.0.12, 4.4.26, 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: Kenneth Dyer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-78384 mongos should allow --port 0 Closed
Participants:
Days since reply: 17 weeks, 1 day ago

 Description   
Original Downstream Change Summary

Consolidates the verification logic for the listening port (i.e. net.port), so that it accepts values in the following range for mongod, mongos, and mongoq: [0, 65535]

Description of Linked Ticket

mongos, unlike mongod, does not allow listening on an arbitrary OS-assigned port by specifying --port 0.

In ancient times (2010), validation for --port was added to the server.

Then, in slightly less ancient times (2013), this validation was split into separate validation code for mongod and mongos.

And then, in not-even-all-that-long-ago times (2017), the validation for mongod was updated to allow port 0, but no such update was done for the corresponding mongos argument validation.

We should apply that update there as well.



 Comments   
Comment by Sarah Olson [ 10/Oct/23 ]

kenneth.dyer@mongodb.com, we have this backport ticket for backporting to 7.0: https://jira.mongodb.org/browse/DOCS-16430

Because the original docs ticket is in external review, I will close out the backport request and you can backport as part of this ticket. Please give a shout if that doesn't work for you and thanks very much!

Comment by Amirsaman Memaripour [ 28/Sep/23 ]

kenneth.dyer@mongodb.com, sure, SGTM

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