Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#544 closed enhancement (fixed)

Limit proxy_next_upstream

Reported by: Ivan Larionov Owned by:
Priority: minor Milestone:
Component: nginx-core Version: 1.5.x
Keywords: Cc:
uname -a: Linux du4-pre-qa-fe01 2.6.32-5-xen-amd64 #1 SMP Mon Jan 16 20:48:30 UTC 2012 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.4.7
built by gcc 4.7.2 (Debian 4.7.2-5)
TLS SNI support enabled
configure arguments: --user=www-data --group=www-data --prefix=/var/lib/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --http-log-path=/var/log/nginx/access.log --http-client-body-temp-path=/var/lib/nginx/body --http-proxy-temp-path=/var/lib/nginx/proxy --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --with-http_ssl_module --with-debug --with-http_realip_module --with-http_addition_module --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_gzip_static_module --with-http_stub_status_module --with-http_perl_module --with-mail --with-mail_ssl_module --add-module=modules/nginx-upstream-fair --add-module=modules/nginx-auth-pam --add-module=modules/nginx-sla

Description

It could be useful to be able to limit proxy_next_upstream by number of tries or by time.

Something like:

proxy_next_upstream error timeout http_502 http_504;
proxy_next_tries 5;
proxy_next_timeout 10s;

Some past discussions:

maillist:
​http://mailman.nginx.org/pipermail/nginx/2013-April/038424.html
​http://mailman.nginx.org/pipermail/nginx-devel/2013-April/003656.html

forum:
​http://forum.nginx.org/read.php?2,238124,238124

Change History (3)

comment:1 by Roman Arutyunyan <arut@…>, 10 years ago

In d09b689911ac2a3236f0fea322088e586814f9f8/nginx:

Upstream: limited next_upstream time and tries (ticket #544).

The new directives {proxy,fastcgi,scgi,uwsgi,memcached}_next_upstream_tries
and {proxy,fastcgi,scgi,uwsgi,memcached}_next_upstream_timeout limit
the number of upstreams tried and the maximum time spent for these tries
when searching for a valid upstream.

comment:2 by Roman Arutyunyan, 10 years ago

Resolution: → fixed
Status: new → closed

comment:3 by Ivan Larionov, 10 years ago

Awesome! Thank you!

Note: See TracTickets for help on using tickets.