-
Notifications
You must be signed in to change notification settings - Fork 96
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
Scale upstreams tests reports errors because zone size for NGINX Plus upstream #2023
Comments
Problem: Scale test is not part of Github actions pipeline Solution: - Add NFR scale test to GitHub actions pipeline along other NFR tests. - Increase the size of the cluster used for NFR tests, as the scale test requires bigger size. Testing: - Successfully run with NGINX -- #2002 - Successfully run with NGINX Plus -- #2017 Some scale test issues were discovered: - #2023 - #2009 Closes #1927
N+ upstream scale test should only scale to 556 Pods. From the old scale test doc:
|
Problem: Scale test is not part of Github actions pipeline Solution: - Add NFR scale test to GitHub actions pipeline along other NFR tests. - Increase the size of the cluster used for NFR tests, as the scale test requires bigger size. Testing: - Successfully run with NGINX -- #2002 - Successfully run with NGINX Plus -- #2017 Some scale test issues were discovered: - #2023 - #2009 Closes #1927
Does this error prevent us from running the test? As @kate-osborn points out, if we scale to 556, does this error affect us? |
Issue seen again: #2110 Test still runs, just fails to reach scale. |
When scale test runs with NGINX Plus with 648 upstream servers, it reports both NGF and NGINX Plus errors, because at some point the upstream zone size is no longer enough to hold all upstream servers. As a result, NGF fails to update NGINX Plus.
NGF log excerpt:
NGINX Plus log:
Results https://github.com/nginxinc/nginx-gateway-fabric/blob/467fd76acebe746aacdf34426000a74e54fdda4b/tests/results/scale/edge/TestScale_UpstreamServers
Acceptance criteria:
The text was updated successfully, but these errors were encountered: