Re: proxy_read_timeout vs proxy_next_upstream_timeout

2016-03-31 Thread B.R.
On Thu, Mar 31, 2016 at 6:54 PM, Frank Liu wrote: > Given this config: > proxy_next_upstream timeout; > proxy_next_upstream_timeout 50; > proxy_connect_timeout 10; > proxy_read_timeout 100; > If upstream has issues causing connect timeout, nginx will re-try 5 > upstream servers until hitting 50,

Re: proxy_read_timeout vs proxy_next_upstream_timeout

2016-03-31 Thread Frank Liu
Given this config: proxy_next_upstream timeout; proxy_next_upstream_timeout 50; proxy_connect_timeout 10; proxy_read_timeout 100; If upstream has issues causing connect timeout, nginx will re-try 5 upstream servers until hitting 50, then fail. If one upstream has issues causing read timeout, nginx

Re: proxy_read_timeout vs proxy_next_upstream_timeout

2016-03-29 Thread B.R.
Those directives works at very different levels. proxy_next_upstream_timeout allocates a time for nginx to find a proper upstream (configured with proxy_next_upstream

proxy_read_timeout vs proxy_next_upstream_timeout

2016-03-29 Thread Frank Liu
Hi If you set read timeout 2 min and next upstream timeout 50 seconds, will nginx break the current connection at 50 second or will it let the read finish until 2min? Thanks Frank ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/l