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

Increase keepalive-requests from 100 to 1000, the nginx default #5050

Closed
nickzelei opened this issue Feb 7, 2024 · 2 comments · Fixed by #5083
Closed

Increase keepalive-requests from 100 to 1000, the nginx default #5050

nickzelei opened this issue Feb 7, 2024 · 2 comments · Fixed by #5083
Labels
backlog Pull requests/issues that are backlog items proposal An issue that proposes a feature request
Milestone

Comments

@nickzelei
Copy link

nickzelei commented Feb 7, 2024

The default value for keepalive_requests is 1000 as per the nginx docs here. This was changed in version 1.19.10.
However, the ingress controller still defaults this value to 100.

image

https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/configmap-resource/

The same could be said for the timeout, which nginx defaults to 75s, but the controller is still defaulting to 65s.

I was debugging a GOAWAY issue and all of the info I could find around the web pointed to this value. I was relieved to find that the ingress controller was still setting it to a lower value as when bumped to 1000, my issue went away.

@nickzelei nickzelei added the proposal An issue that proposes a feature request label Feb 7, 2024
Copy link

github-actions bot commented Feb 7, 2024

Hi @nickzelei thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

@j1m-ryan
Copy link
Member

j1m-ryan commented Feb 8, 2024

Hi @nickzelei . Thanks for pointing this descrepancy out. It's great to hear you've managed to resolve your GOAWAY issue by adjusting the configmap values in the mean time.

We've initiated a discussion for this topic here as there are some things to think about before adding this to NIC. Your insights would be highly valuable to the discussion, so please consider contributing.

@brianehlert brianehlert added the backlog Pull requests/issues that are backlog items label Feb 8, 2024
@brianehlert brianehlert added this to the v3.5.0 milestone Feb 8, 2024
@brianehlert brianehlert moved this from Todo ☑ to Prioritized Backlog in NGINX Ingress Controller Feb 8, 2024
@shaun-nx shaun-nx moved this from Prioritized Backlog to In Review 👀 in NGINX Ingress Controller Feb 13, 2024
@github-project-automation github-project-automation bot moved this from In Review 👀 to Done 🚀 in NGINX Ingress Controller Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Pull requests/issues that are backlog items proposal An issue that proposes a feature request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants