fix (sagemaker): increase mlflowTrackingServerTimeout #41463
+4
−1
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
As mentioned in issue #41436 , the 30-minute timeout is not always sufficient for creating an MLflow tracking server.. This PR increases the timeout to 45 minutes.
Relations
Closes #41436
References
The
mlflowTrackingServerTimeout
is being used by thewaitMlflowTrackingServerCreated
,waitMlflowTrackingServerUpdated
andwaitMlflowTrackingServerDeleted
functions.