This module requires the service of HTTP, FTP and AJP13 protocols
Load balancing scheduler algorithm is provided by not this
module but other modules such as:
Thus, in order to get the ability of load balancing,
Do not enable proxying until you have secured your server. Open proxy servers are dangerous both to your network and to the Internet at large.
At present, there are 3 load balancer scheduler algorithms available
for use: Request Counting, Weighted Traffic Counting and Pending Request
Counting. These are controlled via the lbmethod value of
the Balancer definition. See the
Before we dive into the technical details, here's an example of
how you might use
Another example of how to provide load balancing with stickyness
using
At present there are 6 environment variables exported:
This is assigned the stickysession value used in the current request. It is the cookie or parameter name used for sticky sessions
This is assigned the route parsed from the current request.
This is assigned the name of the balancer used for the current
request. The value is something like balancer://foo.
This is assigned the name of the worker used for the current request.
The value is something like http://hostA:1234.
This is assigned the route of the worker that will be used for the current request.
This is set to 1 if the session route does not match the worker route (BALANCER_SESSION_ROUTE != BALANCER_WORKER_ROUTE) or the session does not yet have an established route. This can be used to determine when/if the client needs to be sent an updated route when sticky sessions are used.
This module requires the service of
Thus, in order to get the ability of load balancer management,
To enable load balancer management for browsers from the example.com
domain add this code to your httpd.conf
configuration file
You can now access load balancer manager by using a Web browser
to access the page
http://your.server.name/balancer-manager
This directive specifies the protective nonce used in the
balancer-manager application page.
The default is to use an automatically determined UUID-based
nonce, to provide for further protection for the page. If set
to Set, then the next argument sets the nonce to that
value. A setting of None disables all nonce checking.
In addition to the nonce, the balancer-manager page
should be protected via an ACL.