summaryrefslogtreecommitdiff
path: root/docs/manual/mod/mod_proxy_balancer.html.en
diff options
context:
space:
mode:
Diffstat (limited to 'docs/manual/mod/mod_proxy_balancer.html.en')
-rw-r--r--docs/manual/mod/mod_proxy_balancer.html.en23
1 files changed, 13 insertions, 10 deletions
diff --git a/docs/manual/mod/mod_proxy_balancer.html.en b/docs/manual/mod/mod_proxy_balancer.html.en
index 566b42c369..8382b84988 100644
--- a/docs/manual/mod/mod_proxy_balancer.html.en
+++ b/docs/manual/mod/mod_proxy_balancer.html.en
@@ -87,17 +87,20 @@
<li><a href="#comments_section">Comments</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="scheduler" id="scheduler">Load balancer scheduler algorithm</a></h2>
+<h2><a name="scheduler" id="scheduler">Load balancer scheduler algorithm</a><a title="Permanent link" href="#scheduler" class="permalink">&para;</a></h2>
- <p>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 <code>lbmethod</code> value of
+ <p>At present, there are 4 load balancer scheduler algorithms available
+ for use: Request Counting (<code class="module"><a href="../mod/mod_lbmethod_byrequests.html">mod_lbmethod_byrequests</a></code>),
+ Weighted Traffic Counting (<code class="module"><a href="../mod/mod_lbmethod_bytraffic.html">mod_lbmethod_bytraffic</a></code>),
+ Pending Request Counting (<code class="module"><a href="../mod/mod_lbmethod_bybusyness.html">mod_lbmethod_bybusyness</a></code>) and
+ Heartbeat Traffic Counting (<code class="module"><a href="../mod/mod_lbmethod_heartbeat.html">mod_lbmethod_heartbeat</a></code>).
+ These are controlled via the <code>lbmethod</code> value of
the Balancer definition. See the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code>
directive for more information, especially regarding how to
configure the Balancer and BalancerMembers.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="stickyness" id="stickyness">Load balancer stickyness</a></h2>
+<h2><a name="stickyness" id="stickyness">Load balancer stickyness</a><a title="Permanent link" href="#stickyness" class="permalink">&para;</a></h2>
<p>The balancer supports stickyness. When a request is proxied
to some back-end, then all following requests from the same user
@@ -114,7 +117,7 @@
itself. The URL encoding is usually done on the back-end.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="example" id="example">Examples of a balancer configuration</a></h2>
+<h2><a name="example" id="example">Examples of a balancer configuration</a><a title="Permanent link" href="#example" class="permalink">&para;</a></h2>
<p>Before we dive into the technical details, here's an example of
how you might use <code class="module"><a href="../mod/mod_proxy_balancer.html">mod_proxy_balancer</a></code> to provide
@@ -145,7 +148,7 @@ ProxyPassReverse "/test" "balancer://mycluster"</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="environment" id="environment">Exported Environment Variables</a></h2>
+<h2><a name="environment" id="environment">Exported Environment Variables</a><a title="Permanent link" href="#environment" class="permalink">&para;</a></h2>
<p>At present there are 6 environment variables exported:</p>
@@ -198,7 +201,7 @@ ProxyPassReverse "/test" "balancer://mycluster"</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="balancer_manager" id="balancer_manager">Enabling Balancer Manager Support</a></h2>
+<h2><a name="balancer_manager" id="balancer_manager">Enabling Balancer Manager Support</a><a title="Permanent link" href="#balancer_manager" class="permalink">&para;</a></h2>
<p>This module <em>requires</em> the service of
<code class="module"><a href="../mod/mod_status.html">mod_status</a></code>.
@@ -228,7 +231,7 @@ ProxyPassReverse "/test" "balancer://mycluster"</pre>
containers can be dynamically controlled by the Manager.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="stickyness_implementation" id="stickyness_implementation">Details on load balancer stickyness</a></h2>
+<h2><a name="stickyness_implementation" id="stickyness_implementation">Details on load balancer stickyness</a><a title="Permanent link" href="#stickyness_implementation" class="permalink">&para;</a></h2>
<p>When using cookie based stickyness, you need to configure the
name of the cookie that contains the information about which back-end
@@ -285,7 +288,7 @@ ProxyPassReverse "/test" "balancer://mycluster"</pre>
for the same request, the information from the request parameter is used.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="stickyness_troubleshooting" id="stickyness_troubleshooting">Troubleshooting load balancer stickyness</a></h2>
+<h2><a name="stickyness_troubleshooting" id="stickyness_troubleshooting">Troubleshooting load balancer stickyness</a><a title="Permanent link" href="#stickyness_troubleshooting" class="permalink">&para;</a></h2>
<p>If you experience stickyness errors, e.g. users lose their
application sessions and need to login again, you first want to