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

Update jasper_process.py in resmoke to reflect Jasper RPC changes

    XMLWordPrintable

Details

    • Fully Compatible
    • Evergreen 2019-01-28, Evergreen 2019-02-11, Evergreen 2019-02-25, Evergreen 2019-03-11, Evergreen 2019-03-25
    • 1

    Description

      The current implementation for jasper_process.py has some lines of code for handling RPC errors from Jasper when it does things like signal a process that has already terminated somehow.

      This is not reflective of how Jasper actually handles such errors after the completion of MAKE-525, and therefore should be changed to check for these conditions in the val case.

      Not doing this causes a test failure in replica_sets_kill_secondaries_jscore_passthrough, in which resmoke exhibits inconsistent behavior where it sends SIGKILL/SIGTERM to processes, and then expects the same processes to be alive at a later time. The full description of this problem can be found at this comment.

      Attachments

        Activity

          People

            kimberly.tao@mongodb.com Kim Tao
            may.hoque@mongodb.com May Hoque
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: