JobTracker requires application IDs #632 #638
Merged
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
Closed
Closed
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.
Preparing to read tracked jobs from EJR instead of ZK.
#635 will currently fetch a lot of jobs from EJR, including those that were never actually started. This mimics the ZK implementation in a way (it will just get those in the
/ongoingbranch) but that one employs auser_limitto keep requests down; this uses a different strategy and if this thing works in ZK, we can just port it to EJR.The rationale is that
JobTrackerrequires an application ID in order to do something useful (= use this application ID to fetch the state of the underlying application and update the job status).