Httpd BalancerMember: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
Adds a member to [[Httpd_mod_proxy_Concepts#Balancer_Workers|a load balancing group]]. It can be used with a <Proxy> container directive and can take any of the key-value pair parameters available to [[httpd ProxyPass|ProxyPass]]. | Adds a member to [[Httpd_mod_proxy_Concepts#Balancer_Workers|a load balancing group]]. It can be used with a <Proxy> container directive and can take any of the key-value pair parameters available to [[httpd ProxyPass|ProxyPass]]. | ||
BalancerMember can be used outside of a <Proxy> container, and in this case the "balancerurl" (see [[#Syntax|Syntax]] below) is required and it corresponds to the URL of the balancer defined in the ProxyPass directive. | |||
==loadfactor== | ==loadfactor== | ||
Revision as of 03:15, 23 December 2016
External
Internal
Overview
Adds a member to a load balancing group. It can be used with a <Proxy> container directive and can take any of the key-value pair parameters available to ProxyPass.
BalancerMember can be used outside of a <Proxy> container, and in this case the "balancerurl" (see Syntax below) is required and it corresponds to the URL of the balancer defined in the ProxyPass directive.
loadfactor
One additional parameter available only to BalancerMember directives is "loadfactor". It is a number between 1 (default) and 100 that defines the weighted load to be applied to the member in question.
Syntax
BalancerMember [balancerurl] url [key=value [key=value ...]]
Example
ProxyPass "/example" "balancer://mycluster/"
<Proxy balancer://mycluster>
BalancerMember http://node1/
BalancerMember http://node2/
</Proxy>