[SERVER-7306] Mongod as windows service should not claim to be 'started' until it is ready to accept connections Created: 09/Oct/12  Updated: 31/Oct/16  Resolved: 28/Oct/16

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 2.0.6, 2.2.0
Fix Version/s: 3.4.0-rc2

Type: Bug Priority: Major - P3
Reporter: Steve Green Assignee: Mark Benvenuto
Resolution: Done Votes: 1
Labels: Windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2008 R2


Issue Links:
Related
related to SERVER-16292 mongod isn't ready for connections wh... Closed
Backwards Compatibility: Fully Compatible
Operating System: Windows
Sprint: Platforms 2016-10-31
Participants:

 Description   

When mongod is started as a Windows service, it reports to the SCM that it has started prior to being able to accept client connections. When a service depends on the mongod service, it seems reasonable for that service to be able to connect to mongod when it has reported that it has started. As the size of the database increases, this is almost never the case. It does not seem reasonable for the mongodb 'client' service to make connection attempts in a loop, as this mechanism would also require a maximum wait time (in the case where mongodb doesn't ever reach the state of accepting connections.

This issue was discussed with Tad Marshall at

http://stackoverflow.com/questions/12788480/windows-scm-reports-that-mongodb-has-started-yet-initial-connections-to-mongodb



 Comments   
Comment by Githook User [ 28/Oct/16 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-7306 Mongod as windows service should not claim to be 'started' until it is ready to accept connections
Branch: master
https://github.com/mongodb/mongo/commit/bb8640fbfaa195a0b6931a60dc72ccfa88376331

Comment by Mark Benvenuto [ 25/Oct/16 ]

This is the Windows version of SERVER-16292. We simply need to not report SERVICE_RUNNING until after the listener is open. We need to follow the pattern of signalForkSuccess.

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