nginx.git/src/stream/ngx_stream_upstream.c, branch release-1.28.1 nginx Upstream: per-upstream resolver. 2024-11-07T15:57:42+00:00 Vladimir Homutov vl@nginx.com 2019-10-18T13:33:15+00:00 ea4654550ab021b5576c03b708079e3ce3e5d9ed The "resolver" and "resolver_timeout" directives can now be specified directly in the "upstream" block. 
The "resolver" and "resolver_timeout" directives can now be specified
directly in the "upstream" block.
 Upstream: construct upstream peers from DNS SRV records. 2024-11-07T15:57:42+00:00 Dmitry Volyntsev xeioex@nginx.com 2016-03-17T15:42:31+00:00 9fe119b431c957824d7bed75fce47dfbda74ca33 






Upstream: re-resolvable servers.
2024-11-07T15:57:42+00:00

Ruslan Ermilov
ru@nginx.com

2014-02-15T11:12:34+00:00

db6870e06dde7ab249e9a41a0e0a76219f82dd8c

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>




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>






Upstream: revised upstream response time variables.
2018-11-21T10:40:40+00:00

Vladimir Homutov
vl@nginx.com

2018-11-21T10:40:40+00:00

c24146731810f2711da608cd7f3bdca528a3eb14

Variables now do not depend on presence of the HTTP status code in response.
If the corresponding event occurred, variables contain time between request
creation and the event, and "-" otherwise.

Previously, intermediate value of the $upstream_response_time variable held
unix timestamp.





Variables now do not depend on presence of the HTTP status code in response.
If the corresponding event occurred, variables contain time between request
creation and the event, and "-" otherwise.

Previously, intermediate value of the $upstream_response_time variable held
unix timestamp.







Variables: macros for null variables.
2017-08-01T11:28:33+00:00

Ruslan Ermilov
ru@nginx.com

2017-08-01T11:28:33+00:00

b992f7259ba4763178f9d394b320bcc5de88818b

No functional changes.





No functional changes.







Upstream: max_conns.
2016-09-22T16:32:47+00:00

Ruslan Ermilov
ru@nginx.com

2016-09-22T16:32:47+00:00

f674f32c09c9938d5f2b19509166e5c5e28a9e3c












Fixed log levels of configuration parsing errors.
2016-09-20T12:07:16+00:00

Valentin Bartenev
vbart@nginx.com

2016-09-20T12:07:16+00:00

89f82c1155d0e2291f30819c38d438e112ba569a

All the errors that prevent loading configuration must be printed on the "emerg"
log level.  Previously, nginx might silently fail to load configuration in some
cases as the default log level is "error".





All the errors that prevent loading configuration must be printed on the "emerg"
log level.  Previously, nginx might silently fail to load configuration in some
cases as the default log level is "error".







Stream: upstream response time variables.
2016-09-02T15:27:12+00:00

Vladimir Homutov
vl@nginx.com

2016-09-02T15:27:12+00:00

443b52db591d876a0e10b9ac3406174eb7fdbce1

The $upstream_connect_time, $upstream_first_byte_time and
$upstream_session_time variables keep corresponding times.





The $upstream_connect_time, $upstream_first_byte_time and
$upstream_session_time variables keep corresponding times.







Stream: $upstream_bytes_sent and $upstream_bytes_received.
2016-09-02T15:27:08+00:00

Vladimir Homutov
vl@nginx.com

2016-09-02T15:27:08+00:00

64223df67078cec444cdf71584015036c68dcc32












Stream: the $upstream_addr variable.
2016-09-02T15:27:05+00:00

Vladimir Homutov
vl@nginx.com

2016-09-02T15:27:05+00:00

c6d456da87fab9fc953f4f0d8506ac83415e774c

Keeps the full address of the upstream server.  If several servers were
contacted during proxying, their addresses are separated by commas,
e.g. "192.168.1.1:80, 192.168.1.2:80".





Keeps the full address of the upstream server.  If several servers were
contacted during proxying, their addresses are separated by commas,
e.g. "192.168.1.1:80, 192.168.1.2:80".