[SERVER-79953] resmoke stepdown thread should check the exit code of mongod during clean shutdown Created: 11/Aug/23 Updated: 29/Oct/23 Resolved: 18/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Jiawei Yang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2023-08-21 | ||||
| Participants: | |||||
| Linked BF Score: | 135 | ||||
| Description |
|
It is possible for the server process to have crashed at shutdown rather than exiting with code 0. We should surface this condition as a ServerFailure exception to halt further test execution to avoid confounding the original error. This can be accomplished by checking the return value from chosen.mongod.wait() in restart_node(). |
| Comments |
| Comment by Githook User [ 18/Aug/23 ] |
|
Author: {'name': 'Jiawei Yang', 'email': 'jiawei.yang@mongodb.com', 'username': 'YoungYang0820'}Message: |