update executions in status 'running' at start-up #90
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
pingali
added a commit
to pingali/ndscheduler
that referenced
this pull request
Jan 27, 2021
… is running. Copy of the pull to the base repo. Nextdoor#90
pingali
added a commit
to pingali/ndscheduler
that referenced
this pull request
Jan 27, 2021
… is running. Copy of the pull to the base repo. Nextdoor#90
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.
This PR fixes the issue raised in #86.
At start-up the executions in the database are searched for entries in state "scheduled", "running", or "stopping" which are assumed to be left-overs caused by previously interrupted ndscheduler.
The status of this entries is set to "failed" and the result is set to { "error": "interrupted"}.