Increase endpointInServiceTimeout from 10m to 60m #39090
Merged
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.
Description
SageMaker endpoints are now taking a little over 10 minutes to become InService. This aligns the hardcoded endpoint timeout to 60 minutes.
This primarily effects SageMaker serverless endpoints. As an example, a test endpoint that deploys in >10m is using an xgboost model and associated container.
i.e.
Relations
Closes #0000
References
Output from Acceptance Testing