[DOCS-10609] Docs for SERVER-9384: Unix domain socket name does not allow for multiple mongods on the same port but different bind_ips Created: 31/Jul/17  Updated: 29/Oct/23  Resolved: 06/Oct/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.5.11

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Andrew Aldridge
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-9384 Unix domain socket name does not allo... Closed
Participants:
Days since reply: 6 years, 18 weeks, 5 days ago
Epic Link: DOCS: 3.6 Server
Story Points: 0.5

 Description   

Documentation Request Summary:

With the new transport layer, you can specify custom unix socket paths in the bind_ip (e.g. --bind_ip=127.0.0.1,/tmp/customsock.sock)

Engineering Ticket Description:

This issue is dependent on SERVER-9383 being implemented, and is specific to the use case of running multiple mongods on the same server using a common port value but different bind_ip settings.

The unix domain socket name is currently mongodb-#####.sock where ##### is the port number. This file naming convention does not allow more than one mongod on port ##### to have a unix domain socket.

The unix domain socket name should be unique based on the bind_ip and port number.



 Comments   
Comment by Githook User [ 06/Oct/17 ]

Author:

{'email': 'i80and@foxquill.com', 'name': 'Andrew Aldridge', 'username': 'i80and'}

Message: DOCS-10609: bind_ip Unix domain sockets
Branch: master
https://github.com/mongodb/docs/commit/b6c054b8580b8eed905cf88f849805f6178fd8cf

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