Repository navigation
Fix Exie ingress request timeout - #2510
Merged
Merged
Conversation
|
This file contains hidden or 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.
Summary
Why
Exie streams can span multiple provider and tool rounds. Although Application Gateway accepted
requestTimeout: 0s, affected browser requests were reset around the default 60-second boundary withERR_HTTP2_PROTOCOL_ERROR. An explicit bounded timeout provides headroom beyond Exie's two-minute turn limit.Validation
helm lint k8s/exceptionlesshelm lint k8s/exceptionless -f k8s/ex-dev-values.yamlhelm lint k8s/exceptionless -f k8s/ex-prod-values.yaml0s, development3m, production3m10stimed out at 10.008s and 10.007s;3mallowed the same endpoint to complete after 79.599s without an HTTP/2 resetBreaking changes
None.