Increase the webdav receive_timeout to 120 seconds #3010
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
We were hitting the 60 second default timeout when uploading a large app. This timeout is used after the PUT to the blobstore when the httpclient is trying to read the headers for the response. Since the blobstore is busy processing the large upload, it was taking longer than 60 seconds to start the response. Currently not configurable but should be easy to thread it through the config if that becomes needed later. Signed-off-by: Joseph Palermo <[email protected]>
will-gant
pushed a commit
to sap-contributions/cloud_controller_ng
that referenced
this pull request
Oct 20, 2022
We were hitting the 60 second default timeout when uploading a large app. This timeout is used after the PUT to the blobstore when the httpclient is trying to read the headers for the response. Since the blobstore is busy processing the large upload, it was taking longer than 60 seconds to start the response. Currently not configurable but should be easy to thread it through the config if that becomes needed later. Signed-off-by: Joseph Palermo <[email protected]> Signed-off-by: Joseph Palermo <[email protected]> Co-authored-by: Merric de Launey <[email protected]>
will-gant
pushed a commit
to sap-contributions/cloud_controller_ng
that referenced
this pull request
Dec 16, 2022
We were hitting the 60 second default timeout when uploading a large app. This timeout is used after the PUT to the blobstore when the httpclient is trying to read the headers for the response. Since the blobstore is busy processing the large upload, it was taking longer than 60 seconds to start the response. Currently not configurable but should be easy to thread it through the config if that becomes needed later. Signed-off-by: Joseph Palermo <[email protected]> Signed-off-by: Joseph Palermo <[email protected]> Co-authored-by: Merric de Launey <[email protected]>
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.
We were hitting the 60 second default timeout when uploading a large app. This timeout is used after the PUT to the blobstore when the httpclient is trying to read the headers for the response. Since the blobstore is busy processing the large upload, it was taking longer than 60 seconds to start the response.
Currently not configurable but should be easy to thread it through the config if that becomes needed later.
Update the blobstore max_upload_size default to remove upload size limit capi-release#274