nginx.git - nginx

Age	Commit message (Collapse)	Author	Files	Lines
2024-11-07	Upstream: re-resolvable servers.	Ruslan Ermilov	1	-0/+12
	Specifying the upstream server by a hostname together with the "resolve" parameter will make the hostname to be periodically resolved, and upstream servers added/removed as necessary. This requires a "resolver" at the "http" configuration block. The "resolver_timeout" parameter also affects when the failed DNS requests will be attempted again. Responses with NXDOMAIN will be attempted again in 10 seconds. Upstream has a configuration generation number that is incremented each time servers are added/removed to the primary/backup list. This number is remembered by the peer.init method, and if peer.get detects a change in configuration, it returns NGX_BUSY. Each server has a reference counter. It is incremented by peer.get and decremented by peer.free. When a server is removed, it is removed from the list of servers and is marked as "zombie". The memory allocated by a zombie peer is freed only when its reference count becomes zero. Co-authored-by: Roman Arutyunyan <arut@nginx.com> Co-authored-by: Sergey Kandaurov <pluknet@nginx.com> Co-authored-by: Vladimir Homutov <vl@nginx.com>
2016-09-22	Upstream: max_conns.	Ruslan Ermilov	1	-0/+9

2016-09-22	Upstream: removed the quick recovery mechanism.	Ruslan Ermilov	1	-6/+0
	Its usefulness it questionable, and it interacts badly with max_conns.
2016-09-22	Upstream: style.	Maxim Dounin	1	-1/+0

2016-03-30	Style.	Ruslan Ermilov	1	-1/+1

2015-04-14	Upstreams: locking.	Ruslan Ermilov	1	-0/+10

2015-04-10	Upstream: store peers as a linked list.	Ruslan Ermilov	1	-10/+11
	This is an API change.
2015-04-10	Upstream: track the number of active connections to upstreams.	Ruslan Ermilov	1	-120/+18
	This also simplifies the implementation of the least_conn module.
2014-09-12	Upstream: included backup peers into peer.tries.	Roman Arutyunyan	1	-5/+0
	Since peer.tries is never reset it can now be limited if required.
2013-05-21	Upstream: fixed fail_timeout and max_fails > 1.	Maxim Dounin	1	-1/+4
	Due to peer->checked always set since rev. c90801720a0c (1.3.0) by round-robin and least_conn balancers (ip_hash not affected), the code in ngx_http_upstream_free_round_robin_peer() function incorrectly reset peer->fails too often. Reported by Dmitry Popov, http://mailman.nginx.org/pipermail/nginx-devel/2013-May/003720.html
2013-04-12	Upstream: warn if multiple non-stackable balancers are installed.	Ruslan Ermilov	1	-0/+5

2013-03-25	Upstream: removed double-free workarounds in peer.free() methods.	Ruslan Ermilov	1	-4/+0

2012-12-25	Upstream: fixed state resetting when switching to backup servers.	Valentin Bartenev	1	-1/+3
	Based on patch by Thomas Chen (ticket #257).
2012-07-24	Fixed compilation with -Wmissing-prototypes.	Ruslan Ermilov	1	-1/+1

2012-06-04	Upstream: least_conn compilation fixes.	Maxim Dounin	1	-5/+3
	Removed duplicate call of ngx_http_upstream_init_round_robin_peer() overlooked during code changes. Rewritten "return lcp->free_rr_peer(...)" as MSVC doesn't like it.
2012-06-03	Upstream: least_conn balancer module.	Maxim Dounin	1	-0/+404