Crash Krill if a fatal error is encountered by the task scheduler. #1132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timbru
pushed a commit
that referenced
this pull request
Oct 3, 2023
timbru
pushed a commit
that referenced
this pull request
Oct 17, 2023
…1132) * Crash Krill if a fatal error is encountered by the task scheduler. * Do not finish running task when just adding a new task.
timbru
pushed a commit
that referenced
this pull request
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note that FatalError is only used for issues in using the storage. We can't recover from that.
If the storage issues are resolved and Krill restarts, it will also schedule any missing tasks. If that scheduling fails, then this is again a fatal error. This is by design. Someone should look at the issue.