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

mongo shell shutdown: signal handler race?

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Platforms 2018-08-27
    • 25

      The logs of BFGs attached to https://jira.mongodb.org/browse/BF-10120 shows a unit test js_test:user_cache_doc_source succeeding.

      It launches a mongo shell (with

      startParallelShell

      ) and a mongod server. The server shuts down cleanly, but the mongo shell does not, dying from the SIGTERM. (pid 15354 is the spawned 'mongo' process)

      [js_test:user_cache_doc_source] 2018-08-03T18:23:06.819+0000 terminating the following processes started by jstests/auth/user_cache_doc_source.js: 15354
      [js_test:user_cache_doc_source] 2018-08-03T18:23:06.821+0000 2018-08-03T18:23:06.821+0000 I - [main] Process with pid 15354 exited with error code -15
      [js_test:user_cache_doc_source] 2018-08-03T18:23:06.821+0000 one more more child processes exited with an error during jstests/auth/user_cache_doc_source.js

       
      https://logkeeper.mongodb.org/lobster/build/85c97cc526eeaeffc622a55464085e27/test/5b63b673c2ab6838a8031998#bookmarks=0%2C49%2C110%2C127

       

      Hypothesis: The test refactoring of SERVER-36384 affected this test, and maybe the lifespan of these spawned processes is very short now, exposing a job control bug.

            Assignee:
            billy.donahue@mongodb.com Billy Donahue
            Reporter:
            billy.donahue@mongodb.com Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: