[SERVER-40518] backup_restore*.js tests send SIGTERM to resmoke.py and may leak mongo shell running FSM workloads Created: 07/Apr/19 Updated: 29/Oct/23 Resolved: 09/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | STM 2019-04-22 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 10 | ||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||
| Description |
|
Sending a SIGTERM to resmoke.py causes the Python process to immediately exit (it doesn't register a handler for that signal like the server does) without waiting for any of the mongo shell processes it spawned to also exit (though they also receive the SIGTERM signal). This means if resmoke.py was in the midst of spawning a mongo shell process to run an FSM workload, then it could continue to run (i.e. be leaked) even after the parent resmoke.py process exits. |
| Comments |
| Comment by Githook User [ 09/Apr/19 ] |
|
Author: {'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}Message: |