move maxconn from each backend to the overall configuration
controlling the number of connection for each backend is not enough and won't work if the number is bigger than default maxconn, which takes precedence for overall frontend and backend session limit, so move the maxconn for each service to the overall configuration instead of a particular backend node. Change-Id: I971d93eab7424639a0fb5f0705f94ac9c6931044
This commit is contained in:
parent
00944b8c36
commit
822ffe7d1d
@ -66,8 +66,11 @@ listen {{name}}
|
||||
{{#options}}
|
||||
{{.}}
|
||||
{{/options}}
|
||||
{{#service_maxconn}}
|
||||
maxconn {{.}}
|
||||
{{/service_maxconn}}
|
||||
{{#nodes}}
|
||||
server {{name}} {{ip}}:{{port}} check inter 2000 rise 2 fall 5 {{#service_maxconn}}maxconn {{.}}{{/service_maxconn}} {{#extra_server_params}} {{.}}{{/extra_server_params}}
|
||||
server {{name}} {{ip}}:{{port}} check inter 2000 rise 2 fall 5 {{#extra_server_params}} {{.}}{{/extra_server_params}}
|
||||
{{/nodes}}
|
||||
{{/services}}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user