[SERVER-9384] Unix domain socket name does not allow for multiple mongods on the same port but different bind_ips Created: 18/Apr/13  Updated: 06/Dec/17  Resolved: 26/Jul/17

Status: Closed
Project: Core Server
Component/s: Usability
Affects Version/s: 2.2.4, 2.4.1
Fix Version/s: 3.5.11

Type: New Feature Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Jonathan Reams
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-9383 Unix domain socket is not created if ... Closed
depends on SERVER-29403 Implement TransportLayerASIO Closed
Documented
is documented by DOCS-10609 Docs for SERVER-9384: Unix domain soc... Closed
Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-06-19, Platforms 2017-07-10, Platforms 2017-07-31
Participants:

 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 Jonathan Reams [ 26/Jul/17 ]

In SERVER-29403, we allow binding to custom UNIX socket paths, so you don't have to use the default UNIX socket naming convention of /tmp/mongod-port.sock. I think that will let you resolve this issue.

Comment by Githook User [ 26/Jul/17 ]

Author:

{'email': 'jbreams@mongodb.com', 'username': 'jbreams', 'name': 'Jonathan Reams'}

Message: SERVER-9384 Improve testing of UNIX sockets
Branch: master
https://github.com/mongodb/mongo/commit/8235ad20a6169b8713ffba991afcd50519e1345b

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