<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/link/2515316">
<title>Public marks on http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch</title>
<description>Public marks on http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch</description>
<link>http://blogmarks.net/marks/link/2515316</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/camel/mark/1057707622"/>
<rdf:li resource="http://blogmarks.net/api/user/falko/mark/1057527141"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/camel/mark/1057707622">
<title>Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Etch | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch</link>
<description>This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you can use it with any web application that makes use of sessions (such as forums, shopping carts, etc.).

From the HAProxy web site: &quot;HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing. Supporting tens of thousands of connections is clearly realistic with todays hardware. Its mode of operation makes its integration into existing architectures very easy and riskless, while still offering the possibility not to expose fragile web servers to the Net.&quot;</description>
<dc:date>2008-02-21T13:32:57Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>linux, web, debian, apache, application, configuration, load, balancing, availability</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch">Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Etch | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2515316">1 other(s)</a> 
<p class="description">This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you can use it with any web application that makes use of sessions (such as forums, shopping carts, etc.).

From the HAProxy web site: "HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing. Supporting tens of thousands of connections is clearly realistic with todays hardware. Its mode of operation makes its integration into existing architectures very easy and riskless, while still offering the possibility not to expose fragile web servers to the Net."</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application">application</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/configuration">configuration</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/balancing">balancing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/availability">availability</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057707622">Copy</a> | 
<a href="http://blogmarks.net/link/2515316">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/falko/mark/1057527141">
<title>Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Etch | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch</link>
<description>This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you can use it with any web application that makes use of sessions (such as forums, shopping carts, etc.).</description>
<dc:date>2007-11-07T12:00:08Z</dc:date>
<dc:author>falko</dc:author>
<dc:subject>haproxy, heartbeat, load balancer, virtual ip, shared ip, debian, etch, debian etch, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-debian-etch">Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Etch | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/falko">falko</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2515316">1 other(s)</a> 
<p class="description">This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you can use it with any web application that makes use of sessions (such as forums, shopping carts, etc.).</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/haproxy">haproxy</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/heartbeat">heartbeat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load%2Bbalancer">load balancer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/virtual%2Bip">virtual ip</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/shared%2Bip">shared ip</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/etch">etch</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian%2Betch">debian etch</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057527141">Copy</a> | 
<a href="http://blogmarks.net/link/2515316">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>