[SERVER-39094] Update jasper_process.py in resmoke to reflect Jasper RPC changes Created: 18/Jan/19 Updated: 29/Oct/23 Resolved: 15/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | May Hoque | Assignee: | Kim Tao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Evergreen 2019-01-28, Evergreen 2019-02-11, Evergreen 2019-02-25, Evergreen 2019-03-11, Evergreen 2019-03-25 |
| Participants: | |
| Story Points: | 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. |
| Comments |
| Comment by Githook User [ 15/Mar/19 ] |
|
Author: {'email': 'kimberly.tao@mongodb.com', 'name': 'Kim Tao'}Message: |
| Comment by Kim Tao [ 08/Mar/19 ] |
|
Code review URL: https://mongodbcr.appspot.com/431900001/ |