adding a max_fails parameter to upstream member[s] #675
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.
As defined in nginx upstream documentation: http://nginx.org/en/docs/http/ngx_http_upstream_module.html#upstream
I added this optional parameter because we folks have to deal with a finicky backend that randomly timeout on a single request when under heavy load. When this happens, the upstream gets disabled for 10 seconds (fail_timeout) and for that period of time other upstreams receive the requests which doesn't play nice with our application.
Increasing this parameter to max_fails=3 ensures that load is switched only when really necessary.
becomes s:
Let me know if I should change anything, thanks