[SERVER-21197] sockets are opened prior to checking for lock file Created: 29/Oct/15  Updated: 04/Jan/17  Resolved: 13/Jan/16

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.3.1

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Adam Midvidy
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Sprint: Integration F (02/01/16)
Participants:
Linked BF Score: 0

 Description   

We used to check for the lock file before opening sockets. This produced a better error message when inadvertently starting two copies of mongod pointing to the same dbpath and using the same ports.
The bind error message isn't as obvious because we don't know what process is sharing the port; with the lock file, at least we know that mongod is conflicting with another mongod.



 Comments   
Comment by Githook User [ 14/Jan/16 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-21197 test fixes for lockFile changes

Comment by Githook User [ 13/Jan/16 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-21197 make lock_file_fail_to_open more robust
Branch: master
https://github.com/mongodb/mongo/commit/582d669cebbac1733f04dc7738128ab298c314fb

Comment by Githook User [ 13/Jan/16 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-21197 check for existence of lock file prior to opening sockets
Branch: master
https://github.com/mongodb/mongo/commit/c125a557ccc5d452f3b31c3fd025bb07fe355468

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