-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Choreo] Upstream connection handling support considering TCP and HTTP #3625
Open
slahirucd7
wants to merge
3
commits into
wso2:choreo
Choose a base branch
from
slahirucd7:tcpFix
base: choreo
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+93
−12
Open
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -189,6 +189,22 @@ retainKeys = ["self_validate_jwt", "issuer", "claim_mappings", "consumer_key_cla | |||||
# Max interval for the Envoy's exponential retry back off algorithm | ||||||
maxInterval = "500ms" | ||||||
|
||||||
# TCP configurations applicable with the upstream clusters | ||||||
[router.upstream.tcpConfigurations] | ||||||
# The number of milliseconds a connection needs to be idle before keep-alive probes start being sent | ||||||
keepaliveTimeInMillis = 120000 | ||||||
# Maximum number of keep-alive probes to send without response before deciding the connection is dead | ||||||
keepaliveProbes = 9 | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Too high again?
Suggested change
|
||||||
# The number of milliseconds between keep-alive probes | ||||||
keepaliveIntervalInMillis = 75 | ||||||
slahirucd7 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
# HTTP configurations applicable with the upstream clusters | ||||||
[router.upstream.httpConfigurations] | ||||||
# Idle timeout in milliseconds for connections | ||||||
idleTimeoutInMillis = 120000 | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is too low for default. We have to set a value which is more than max response timeout (300s)
Suggested change
|
||||||
# The maximum duration of a connection in milliseconds | ||||||
maxConnectionDurationInMillis = 120000 | ||||||
slahirucd7 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
# Timeouts managed by the connection manager | ||||||
[router.connectionTimeout] | ||||||
# The amount of time that Envoy will wait for the entire request to be received. Time from client to upstream. | ||||||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.