Update jasper_process.py in resmoke to reflect Jasper RPC changes

XMLWordPrintableJSON

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

      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.

              Assignee:
              Kim Tao
              Reporter:
              May Hoque
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: