[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-bugdb
Subject:    general/5137: Busy Virtual Host's can starve other virtual-hosts on the same machine / httpd instanc
From:       Karl Pielorz <karl.pielorz () dmpriest ! com>
Date:       1999-09-29 9:51:00
[Download RAW message or body]


>Number:         5137
>Category:       general
>Synopsis:       Busy Virtual Host's can starve other virtual-hosts on the same machine / httpd instance.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Oct 12 20:10:28 PDT 1999
>Last-Modified:
>Originator:     karl.pielorz@dmpriest.com
>Organization:
apache
>Release:        1.3.9
>Environment:
n/a - Not a bug, a suggesion
>Description:
With a server setup to handle a large number of <Virtual Host>'s, it's possible
that if one virtual server gets exceptionally busy (e.g. is suffering heavy
load, or a Denial of Service attack) - it's repeated requests can stop other
Virtual Servers from being serviced (rather obvious really). This is bad, and
probably likely to get worse as more people swicth to name-based virtual servers,
and stack more servers up per 'httpd instance'.
>How-To-Repeat:
Setup a server with say 50 Virtual Host's, then launch rapid and repeated
requests to just one of these virtual hosts, the others obviously end up 'starved'
of httpd resources. The problem can be made worse if the requests to the popular
server are to fetch a large image / download etc.
>Fix:
Perhaps add something like the ability to set a 'MaxClients' option, which can
be set on a per-virtual server basis? So that no one virtual server can consume
all the available 'MaxClients' of the root httpd process? Maybe even make it a
'percentage' setting?
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

[prev in list] [next in list] [prev in thread] [next in thread]