Add max_conns limit to nginx config #5191
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Another lesson learned. Nginx will happily kill the webui by forwarding many more requests than it can handle, resulting in batches of 502 Bad Gateway errors. Setting
max_conns
to the exact number of connections the app server can handle fixes that problem. This is especially important when the app server runs in prefork mode with a connection limit of one per worker, as is the case for O3.Progress: https://progress.opensuse.org/issues/129490