-
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
base: choreo
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -189,6 +189,20 @@ 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] | ||||||
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.
Suggested change
|
||||||
# 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 = 75000 | ||||||
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. Isn't this too high? Wouldn't something like 30s be better?
Suggested change
|
||||||
|
||||||
# HTTP configurations applicable with the upstream clusters | ||||||
[router.upstream.hTTPConfigurations] | ||||||
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.
Suggested change
|
||||||
# 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
|
||||||
|
||||||
# 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. | ||||||
|
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.