Skip to content
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

Merged
merged 2 commits into from
Nov 2, 2021

Conversation

tsaarni
Copy link
Member

@tsaarni tsaarni commented Nov 2, 2021

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

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>
@tsaarni tsaarni requested a review from a team as a code owner November 2, 2021 16:21
@tsaarni tsaarni requested review from stevesloka and skriss and removed request for a team November 2, 2021 16:21
Signed-off-by: Tero Saarni <tero.saarni@est.tech>
@tsaarni tsaarni added the release-note/small A small change that needs one line of explanation in the release notes. label Nov 2, 2021
@codecov
Copy link

codecov bot commented Nov 2, 2021

Codecov Report

Merging #4151 (c5ef018) into main (5c65e8a) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #4151   +/-   ##
=======================================
  Coverage   72.56%   72.56%           
=======================================
  Files         115      115           
  Lines       10032    10032           
=======================================
  Hits         7280     7280           
  Misses       2597     2597           
  Partials      155      155           
Impacted Files Coverage Δ
internal/envoy/v3/cluster.go 100.00% <100.00%> (ø)
internal/featuretests/v3/envoy.go 100.00% <100.00%> (ø)

@sunjayBhatia sunjayBhatia added this to the 1.20.0 milestone Nov 2, 2021
Copy link
Member

@sunjayBhatia sunjayBhatia left a 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

@tsaarni
Copy link
Member Author

tsaarni commented Nov 2, 2021

@sunjayBhatia This https://github.com/projectcontour/contour/runs/4082714409?check_suite_focus=true#step:6:831
might be same flake as discussed earlier?

• [FAILED] [61.230 seconds]
HTTPProxy
/home/runner/work/contour/contour/test/e2e/httpproxy/httpproxy_test.go:58
  cookie-rewriting
  /home/runner/work/contour/contour/test/e2e/httpproxy/httpproxy_test.go:336
    with namespace: app-cookie-rewrite
    /home/runner/work/contour/contour/test/e2e/framework.go:225
      [It] cookies from app can be rewritten
      /home/runner/work/contour/contour/test/e2e/httpproxy/cookie_rewrite_test.go:183

Though PR #4147 was included in this already...

Copy link
Member

@skriss skriss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sunjayBhatia
Copy link
Member

@sunjayBhatia This https://github.com/projectcontour/contour/runs/4082714409?check_suite_focus=true#step:6:831 might be same flake as discussed earlier?

• [FAILED] [61.230 seconds]
HTTPProxy
/home/runner/work/contour/contour/test/e2e/httpproxy/httpproxy_test.go:58
  cookie-rewriting
  /home/runner/work/contour/contour/test/e2e/httpproxy/httpproxy_test.go:336
    with namespace: app-cookie-rewrite
    /home/runner/work/contour/contour/test/e2e/framework.go:225
      [It] cookies from app can be rewritten
      /home/runner/work/contour/contour/test/e2e/httpproxy/cookie_rewrite_test.go:183

Though PR #4147 was included in this already...

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

@tsaarni
Copy link
Member Author

tsaarni commented Nov 2, 2021

Seems I bumped into another flake
https://github.com/projectcontour/contour/runs/4083566179?check_suite_focus=true#step:6:3740

  	Error Trace:	root_namespaces_test.go:60
  	            				suite.go:724
  	            				asm_amd64.s:1581
  	Error:      	Should be true
  	Test:       	HTTPProxy using root namespaces configured via CLI flag with namespace: root-ns-cli root HTTPProxies outside of root namespaces are not configured
  	Messages:   	expected 200 response code, got 503

@skriss
Copy link
Member

skriss commented Nov 2, 2021

everything's passing now, GH Actions seems happier now - was able to get everything passing on another PR plus main recently.

@skriss skriss merged commit 7fa2a53 into projectcontour:main Nov 2, 2021
@tsaarni
Copy link
Member Author

tsaarni commented Nov 3, 2021

That was really strange one, it took 5 attempts.

By the way, I suppose there is reason why e2e uses --keep-going to ignore errors? The unfortunate side is that it leads into less than ideal troubleshooting experience when one sees test run ending with:

Ran 17 of 17 Specs in 128.420 seconds
SUCCESS! -- 17 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 4 suites in 9m19.082561032s

Test Suite Failed
make: *** [Makefile:288: run-e2e] Error 1
Error: Process completed with exit code 2.

one needs to realize that the failure is buried thousands of lines above the final success suite.

tsaarni added a commit to Nordix/contour that referenced this pull request Nov 3, 2021
…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>
@sunjayBhatia
Copy link
Member

sunjayBhatia commented Nov 3, 2021

--keep-going is to ensure all failures are found in a given suite and that we will run all the test suites, we can choose to bail out early but would lose the ability to see if a change affects multiple tests at a time

(usually what I do is search for [FAIL in the output)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/small A small change that needs one line of explanation in the release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants