<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Language" content="en-us" />
<meta name="ROBOTS" content="ALL" />
<meta http-equiv="imagetoolbar" content="no" />
<meta name="MSSmartTagsPreventParsing" content="true" />
<meta name="Keywords" content="cherokee web server httpd http" />
<meta name="Description" content="Cherokee is a flexible, very fast, lightweight Web server. It is implemented entirely in C, and has no dependencies beyond a standard C library. It is embeddable and extensible with plug-ins. It supports on-the-fly configuration by reading files or strings, TLS/SSL (via GNUTLS or OpenSSL), virtual hosts, authentication, cache friendly features, PHP, custom error management, and much more." />
<link href="media/css/cherokee_doc.css" rel="stylesheet" type="text/css" media="all" />
</head>
<body>
<h2 id="_a_href_index_html_index_a_8594_a_href_modules_html_modules_a_8594_a_href_modules_balancers_html_balancers_a"><a href="index.html">Index</a> → <a href="modules.html">Modules</a> → <a href="modules_balancers.html">Balancers</a></h2>
<div class="sectionbody">
</div>
<h2 id="_balancer_failover">Balancer: Failover</h2>
<div class="sectionbody">
<div class="paragraph"><p>This balancer type is intended to provided a failover or backup server
to fulfill requests only during failure of the machine(s) in the
backend pool.</p></div>
<div class="paragraph"><p>This balancer is very useful when the tendency is to use single
backends to accomodate an existing code base using tracking sessions,
log-ins, etc. In such scenarios, just-in-case balancing might be
required for situations where the main application server fails.</p></div>
<div class="paragraph"><p>If multiple entries are defined, the requests will be serverd through
the first one on the list. When a failure is detected, Cherokee will
kick requests to the next entry on the list for processing. Upon the
application server returning, Cherokee will resume sending traffic to
the original main backend application server for processing.</p></div>
<div class="paragraph"><p>The only thing needed to configure this balancer is a list of
<a href="config_info_sources.html">information sources</a>. At least one must
be selected in order for this to work.</p></div>
</div>
<div id="footer">
<div id="footer-text">
</div>
</div>
</body>
</html>
