apache2 mod_proxy configuration for single threaded servers
- by The Doctor What
I have a multiple instances of thin running behind apache 2.2's mod_proxy. The problem I have is that a couple pages, by design, take a while to run.
If I just configure apache the obvious way (just add the thin urls as BalanceMember lines and no other configurations) then what happens is if someone clicks on the long-running page, then if enough web requests happen while it is running, someone eventually gets the same thin server and has to wait.
Does anyone have some best practices or suggested configuration for mod_proxy and thin?
Ciao!