increase timeout from 300s to 900s #362
Closed
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
The scale up of GPU nodes for large jobs can take up to 10 minutes. So increasing this timeout is needed to wait for all pods to become available.
|
Closing because Mark added this in a separate PR |
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.
The scale up of GPU nodes for large jobs can take up to 10 minutes. So increasing this timeout is needed to wait for all pods to become available.
This change is required to run on 64 nodes with autoscaling enabled. The image pull and VM scale up time are the main reason it takes up to 10 minutes. In some cases the coordinator launches directly while other pods require scale up. In those cases, it's critical that the timeout is set to at least 10 minutes or more.