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

StopMongoProgram shouldn't implicitly switch to SIGKILL

    • Minor Change
    • ALL
    • v3.0
    • 0

      StopMongoProgram (which powers the shell's MongoRunner.stopMongod) will switch to SIGKILL after waiting a while, then still reports successful shutdown. This both masks bugs that deadlock at shutdown and can cause problems for tests that actually need to wait for full clean shutdown. The only indication that this happens is a line in the log, but no one will read that if the test is passing.

      Instead, the shell will now wait forever for a mongod program to terminate via a SIGTERM. If a process indeed is deadlocked at shutdown, resmoke will now run the hang analyzer on the stuck process.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            mathias@mongodb.com Mathias Stearn
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: