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

MongoS service does not restart as per service defined behaviour if all config servers are down

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 3.0.4
    • Fix Version/s: None
    • Component/s: Admin
    • Labels:
      None
    • Environment:
      v3.0.4, Windows 7
    • Operating System:
      ALL

      Description

      On a single-replicaset environment with a MongoS, all servers (mongoD, mongoS and 3 config servers) are configured as Windows services. All services have recovery actions that should cause Windows to restart the services 10 seconds later. Following command is used to specify the recovery action:

      sc failure <mongod/mongos/mongodbconfigX> reset= 0 actions= restart/10000/restart/10000/restart/10000
      

      If all 3 config servers are stopped and the a MongoS is started, MongoS exits (expected), however it does not automatically restart after 10 seconds as specified in the above mentioned service configuration command.

      Following is the output of the sc query mongos:

      SERVICE_NAME: mongos
              TYPE               : 10  WIN32_OWN_PROCESS
              STATE              : 1  STOPPED
              WIN32_EXIT_CODE    : 1066  (0x42a)
              SERVICE_EXIT_CODE  : 5  (0x5)
              CHECKPOINT         : 0x0
              WAIT_HINT          : 0x0
      

      The suspicion is that the Windows doesn't restart MongoS that was exited with a state STOPPED instead of PAUSED.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: