[users@httpd] Limiting vhosts in a shared environment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,
 I'm working on a managed hosting project right now, running Apache
2.  We've got quite a few vhosts set up running on shared hardware.
Today we hit an interesting snag: one host, which gets fairly high
traffic, running Ruby under FastCGI basically hit a condition that
would hang their app.  The servers quickly hit MaxClients thanks to
the hanging app and effectively went offline.  We're now tasked with
preventing this issue in the future, and I'm looking for advice on how
to accomplish this.  I've looked through the available Apache
configuration directives, but none of them seems particularly well
suited toward limiting vhosts from consuming all the apache processes.
The only directives I found were more focused on system resources
(RLimit___) than distribution of vhosts.  This seems to me that it has
to be an issue addressed by other hosting firms, so I'm curious how
it's handled elsewhere.

Thanks,
Matt

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux