On Wed, Apr 14, 2010 at 1:57 PM, Brad Van Sickle <bvs7...@gmail.com> wrote: > My first question relates to quality of service and load balancing: > I'm currently using mod_proxy on the web layer, and I know I can set that up > to load balance requests to multiple app layer nodes, but to the best of my > knowledge mod_proxy is not able to provide any quality of service. So if a > node in the app layer had a problem (or was shut down for maintenance) > mod_proxy would be unaware of that and would still send requests to that > node. How are situations like this normally handled? Is there something I > can use other than mod_proxy that is intelligent enough to mark a host as > down? I'd rather not use a hardware load balancer here if I can avoid it.
Check out perlbal - http://search.cpan.org/dist/Perlbal/ The load balancing is really nice, and you can handle 10k's of clients with junkyard hardware. > My second question deals with management of multiple mod_perl nodes: > At some point, if you have enough app layer nodes, managing the code > deployments, apache configs and server restarts becomes very cumbersome if > you're doing it all manually. Are there any tools that can make these tasks > easier or give me one management view? Puppet and cfmanager are general purpose systems administration tools that serve well here. In addition, you can manage the rest of the system with these tools.
