Welcome! Log In Create A New Profile

Advanced

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

November 16, 2012 10:54AM
Thanks for the reply.

>> What we're actually seeing is that if a a request takes 300+ seconds, the
>> backend is immediately set as disabled and all further requests are send to
>> the other backend...
>> Are we missing something or is this the correct behaviour for nginx?

>Are you looking at the normally working backend server, or a
>server which was already considered down?

One server X receives a request which takes 300+ seconds to complete . That request gets dropped by nginx due to the read timeout (as expected).
When this happens the server X is disabled and all upcoming request are sent to server Y instead.
My interpretation of the configuration was that the server X would still get requests since it only had 1 failure (and it 3 as configured) during the last 30 seconds?
SubjectAuthorPosted

Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 09:15AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim DouninNovember 16, 2012 10:32AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 10:54AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim DouninNovember 16, 2012 11:34AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 11:42AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim DouninNovember 16, 2012 12:12PM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 01:51PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 78
Record Number of Users: 7 on March 06, 2014
Record Number of Guests: 229 on August 01, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready