.NET on the ?Net April 17-23 : Putting it all online
This post is offically quite late. A combination of hackers and the first nice weather in 6 months can be quite distracting. Microsoft has made some big announcements this week around their web strategy. Microsoft?s Salesforce.com competitor, Dynamic...
|Web cluster redundancy with mod_backhand revisited|
In my last blog entry on mod_backhand, I mentioned that you could implement redundancy in a web cluster by having multiple load balancers and using round robin DNS pointing to the load balancers. This technique is mentioned in the mod_backhand presentation notes by Theo Schlossnagle, one of the author's of mod_backhand.
But if you think about it carefully, in my opinion, this solution doesn't really work well:
I can think of several solutions, but the best one as far as I can see (if you still want to use mod_backhand of course) is to run mod_backhand on a high availability hardware solution (or if a few minutes downtime is acceptable, keep a spare box configured with mod_backhand around to swap with any balancer that goes down), and not push the hard problem of high availability and redundancy to DNS.
Ahmad Amran Kapi from Melaka, Malaysia, points out that you can use Wackamole:
Wackamole is an application that helps with making a cluster highly available. It manages a bunch of virtual IPs, that should be available to the outside world at all times. Wackamole ensures that a single machine within a cluster is listening on each virtual IP address that Wackamole manages. If it discovers that particular machines within the cluster are not alive, it will almost immediately ensure that other machines acquire these public IPs. At no time will more than one machine listen on any virtual IP. Wackamole also works toward achieving a balanced distribution of number IPs on the machine within the cluster it manages.
Read more at: http://phplens.com/phpeverywhere/?q=node/view/243.
|< Prev||Next >|