[SERVER-31420] Make PeriodicRunner utility resilient to thrown errors Created: 05/Oct/17 Updated: 08/Jan/24 Resolved: 16/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.5.13 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Mira Carey |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The periodic runner doesn't handle thrown errors gracefully. At the moment, if any single run of a job throws, it will cause an fassert. We should make the runner more resilient to thrown errors within its jobs. |
| Comments |
| Comment by Andy Schwerin [ 05/Oct/17 ] |
|
I think the fassert is correct behavior. I suggest there is nowhere to deliver an exception that escapes a periodic task, so it should be a fatal error for one to escape. |