<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: High-availability Drupal &#8212; File-handling</title>
	<atom:link href="http://www.adamfranco.com/2009/09/09/high-availability-drupal-file-handling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamfranco.com/2009/09/09/high-availability-drupal-file-handling/</link>
	<description>Musings, projects, software, and photography.</description>
	<lastBuildDate>Sun, 22 Jan 2012 19:17:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Adam Franco</title>
		<link>http://www.adamfranco.com/2009/09/09/high-availability-drupal-file-handling/#comment-141</link>
		<dc:creator>Adam Franco</dc:creator>
		<pubDate>Sat, 21 Nov 2009 18:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfranco.com/?p=266#comment-141</guid>
		<description>Hi JJ,

We are currently just using round-robin DNS where the the DNS responses include all of the IP addresses of the web servers, but rotate which one is listed first.

If the host listed first is down, clients will generally try the next host in the list after a timeout period. While this can cause a large decrease in response time when a host goes down, it does provide fail-over abilities without having to add a dedicated load-balancer in front of the web servers.

I&#039;ll post an update if we ever change this set-up, but I doubt that we will ever need to scale to the point where uneven webserver load becomes our pain-point.

- Adam</description>
		<content:encoded><![CDATA[<p>Hi JJ,</p>
<p>We are currently just using round-robin DNS where the the DNS responses include all of the IP addresses of the web servers, but rotate which one is listed first.</p>
<p>If the host listed first is down, clients will generally try the next host in the list after a timeout period. While this can cause a large decrease in response time when a host goes down, it does provide fail-over abilities without having to add a dedicated load-balancer in front of the web servers.</p>
<p>I&#8217;ll post an update if we ever change this set-up, but I doubt that we will ever need to scale to the point where uneven webserver load becomes our pain-point.</p>
<p>- Adam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JJ</title>
		<link>http://www.adamfranco.com/2009/09/09/high-availability-drupal-file-handling/#comment-140</link>
		<dc:creator>JJ</dc:creator>
		<pubDate>Wed, 18 Nov 2009 02:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfranco.com/?p=266#comment-140</guid>
		<description>Nice article and illustrations. However, one point I did not see you address was how to handle and manage the DNS requests for load balancing? Are you assuming a round robin approach? Would like to hear your thoughts on this.

Thx,
JJ</description>
		<content:encoded><![CDATA[<p>Nice article and illustrations. However, one point I did not see you address was how to handle and manage the DNS requests for load balancing? Are you assuming a round robin approach? Would like to hear your thoughts on this.</p>
<p>Thx,<br />
JJ</p>
]]></content:encoded>
	</item>
</channel>
</rss>

