Fix Prediction Job Failures (Aug 2024) #50
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
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.
Changes
wait_for_successparameter on Azure batchmodel'sJobPreparationTaskfrom False (meant to save $$$ in case job prep code failed and left node running indefinitely) to True (wait for file copying to complete before running prediction task).This change is made as an attempt to fix prediction job failures that appear tied to missing file failures (e.g.,
RuntimeError: DataLoader timed out after 600 seconds). The solution tried here fits the symptoms of the failure: rerunning jobs leads to success (just waiting seemed to fix the underlying problem) so perhaps some of the data files had not finished copying over via job preparation task causing the timeout failure.