-
Notifications
You must be signed in to change notification settings - Fork 690
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
internal/envoy: increase default upstream connect timeout #4151
Conversation
This change sets the new default connect timeout to 2 seconds. The default connect timeout was 250 msec which can be too short and may cause failed requests with slow upstream services. Updates projectcontour#2264 Signed-off-by: Tero Saarni <tero.saarni@est.tech>
Signed-off-by: Tero Saarni <tero.saarni@est.tech>
Codecov Report
@@ Coverage Diff @@
## main #4151 +/- ##
=======================================
Coverage 72.56% 72.56%
=======================================
Files 115 115
Lines 10032 10032
=======================================
Hits 7280 7280
Misses 2597 2597
Partials 155 155
|
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.
LGTM given the plan outlined in #2264
@sunjayBhatia This https://github.com/projectcontour/contour/runs/4082714409?check_suite_focus=true#step:6:831
Though PR #4147 was included in this already... |
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.
LGTM
yeah, thought that naive change would fix it having some more flakes generally with e2e tests, might have to do a more detailed assessment soon |
Seems I bumped into another flake
|
everything's passing now, GH Actions seems happier now - was able to get everything passing on another PR plus main recently. |
That was really strange one, it took 5 attempts. By the way, I suppose there is reason why e2e uses
one needs to realize that the failure is buried thousands of lines above the final success suite. |
…tour#4151) This change sets the new default connect timeout to 2 seconds. The default connect timeout was 250 msec which can be too short and may cause failed requests with slow upstream services. Updates projectcontour#2264 Signed-off-by: Tero Saarni <tero.saarni@est.tech>
(usually what I do is search for |
This change sets the new default connect timeout to 2 seconds. The default connect timeout was 250 msec which can be too short and may cause failed requests with slow upstream services.
Updates #2264
Signed-off-by: Tero Saarni tero.saarni@est.tech