[DOCS-7755] Overloading of the term "bind" when describing setting up replica set Created: 26/Apr/16  Updated: 30/Oct/23  Resolved: 29/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Critical - P2
Reporter: Daniel Pasette (Inactive) Assignee: David Hou
Resolution: Done Votes: 0
Labels: reopened
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 11 weeks, 6 days ago
Epic Link: DOCSP-26173

 Description   

https://docs.mongodb.org/manual/tutorial/deploy-replica-set/#architecture

In a production, deploy each member of the replica set to its own machine and if possible bind to the standard MongoDB port of 27017. Use the bind_ip option to ensure that MongoDB listens for connections from applications on configured addresses.

This conflates the meaning of "binding" to a network interface and "listening" on a port.

This is important because when setting up a replica set on separate physical machines, it is required that MongoDB servers listen to an externally accessible network interface.



 Comments   
Comment by David Hou [ 17/Nov/22 ]

emet.ozar@mongodb.com, It looks like Daniel's account is inactive - Is it possible that he's no longer at the company?

Comment by Emet Ozar [ 27/Oct/22 ]

dan@mongodb.com Hey Dan, just wanted to check in to see if this ticket is still relevant? Thank you, Emet CC: sarah.olson@mongodb.com ashley.brown@mongodb.com 

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