Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-7306

Mongod as windows service should not claim to be 'started' until it is ready to accept connections

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.0-rc2
    • Affects Version/s: 2.0.6, 2.2.0
    • Component/s: Admin
    • Labels:
    • Environment:
      Windows Server 2008 R2
    • Fully Compatible
    • Windows
    • Platforms 2016-10-31

      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


            mark.benvenuto@mongodb.com Mark Benvenuto
            slg1013 Steve Green
            1 Vote for this issue
            6 Start watching this issue