That’s a very practical solution for small configurations, and we already use it for some tomcat instances. Unfortunately, when you start dealing with hundreds of appservers in various states, the configuration and load balancing issues add up fast. The mod_cluster configuration model of the appservers advertising their presence and configuring the mod_proxy routes is perfect, just we ran into significant implementation flaws. To get mod_proxy_balancer to work, we would need to build and inject the balancer configurations into the apache instances at runtime (possibly graceful would suffice). I suspect we would also need to add some capacity to account for the lack of backend load balancing, etc. Overall, I think that would be far more disruptive to us than a periodic manual restart of the apache instances when memory creeps up.
Rick Houser Web Administration From: Daniel [mailto:dferra...@gmail.com] Sent: Monday, June 27, 2016 04:30 To: <users@httpd.apache.org> <users@httpd.apache.org> Subject: Re: [users@httpd] Problems with Event MPM Performance Tuning in 2.4.18 As a real mitigation, maybe you could just use to mod_proxy and mod_proxy_balancer, also those are not third party modules and probably will render the same functionality you seek. -- Daniel Ferradal IT Specialist email dferradal at gmail.com<http://gmail.com> linkedin es.linkedin.com/in/danielferradal<http://es.linkedin.com/in/danielferradal>
