Mercurial > hg > nginx-site

comparison xml/en/docs/stream/ngx_stream_upstream_module.xml @ 2470:504536999408

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Added upstream resolver info to upstream server resolve parameter.
author Yaroslav Zhuravlev <yar@nginx.com>
date Wed, 04 Dec 2019 15:36:40 +0300
parents 98fd810c13e0
children 4add6ae1296f
comparison
equal deleted inserted replaced
2469:98fd810c13e0 2470:504536999408
7 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd"> 7 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd">
8 8
9 <module name="Module ngx_stream_upstream_module" 9 <module name="Module ngx_stream_upstream_module"
10 link="/en/docs/stream/ngx_stream_upstream_module.html" 10 link="/en/docs/stream/ngx_stream_upstream_module.html"
11 lang="en" 11 lang="en"
12 rev="38"> 12 rev="39">
13 13
14 <section id="summary"> 14 <section id="summary">
15 15
16 <para> 16 <para>
17 The <literal>ngx_stream_upstream_module</literal> module (1.9.0) 17 The <literal>ngx_stream_upstream_module</literal> module (1.9.0)
233 and automatically modifies the upstream configuration 233 and automatically modifies the upstream configuration
234 without the need of restarting nginx. 234 without the need of restarting nginx.
235 The server group must reside in the <link id="zone">shared memory</link>. 235 The server group must reside in the <link id="zone">shared memory</link>.
236 <para> 236 <para>
237 In order for this parameter to work, 237 In order for this parameter to work,
238 the <link doc="ngx_stream_core_module.xml" id="resolver"/> directive 238 the <literal>resolver</literal> directive
239 must be specified in the 239 must be specified in the
240 <link doc="ngx_stream_core_module.xml" id="stream"/> block. 240 <link doc="ngx_stream_core_module.xml" id="resolver">stream</link> block
241 Example: 241 or in the corresponding <link id="resolver">upstream</link> block.
242 <example>
243 stream {
244 resolver 10.0.0.1;
245
246 upstream u {
247 zone ...;
248 ...
249 server example.com:12345 resolve;
250 }
251 }
252 </example>
253 </para> 242 </para>
254 </tag-desc> 243 </tag-desc>
255 244
256 <tag-name id="service"> 245 <tag-name id="service">
257 <literal>service</literal>=<value>name</value> 246 <literal>service</literal>=<value>name</value>