Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 31023 invoked from network); 17 Sep 2007 09:33:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Sep 2007 09:33:53 -0000 Received: (qmail 69343 invoked by uid 500); 17 Sep 2007 09:33:42 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 69284 invoked by uid 500); 17 Sep 2007 09:33:42 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 69273 invoked by uid 99); 17 Sep 2007 09:33:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Sep 2007 02:33:42 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [193.56.114.156] (HELO smtp2.fr.adp.com) (193.56.114.156) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Sep 2007 09:35:32 +0000 Received: from exchange2k304.gaia.fr ([150.175.10.77]) by smtp2.fr.adp.com (xx/xx) with ESMTP id l8H9XGZh004960 for ; Mon, 17 Sep 2007 11:33:17 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers Date: Mon, 17 Sep 2007 11:33:16 +0200 Message-ID: In-Reply-To: <3B21A253728EA247A10A692547A271530213F70B@EITO-MBX03.internal.vodafone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers Thread-Index: AcfzjRhqfUuD1mE2TnevzUI7nKUWVwAA+J4QAV6G49A= References: <20070910102845.3985622b@grimnir> <3B21A253728EA247A10A692547A271530213F70B@EITO-MBX03.internal.vodafone.com> From: =?iso-8859-1?Q?Axel-St=E9phane__SMORGRAV?= To: X-Virus-Checked: Checked by ClamAV on apache.org -----Message d'origine----- >De : Pl=FCm, R=FCdiger, VF-Group [mailto:ruediger.pluem@vodafone.com]=20 >Envoy=E9 : lundi 10 septembre 2007 12:02 >=C0 : dev@httpd.apache.org >Objet : Re: [PATCH] Apache 2.2.x: Implicit creation of new = proxy_workers > >> -----Urspr=FCngliche Nachricht----- >> Von: Nick Kew >> Gesendet: Montag, 10. September 2007 11:29 >> An: dev@httpd.apache.org >> Betreff: Re: [PATCH] Apache 2.2.x: Implicit creation of new = proxy_workers >>=20 >> Does this open the way to a DoS? If a rewriterule[P] enables = backends=20 >> to be derived from the request URI, then you're creating unlimited=20 >> numbers of workers, which may never be used. Where are the limits on = >> that? > >Also the scoreboard is a limiting factor for this. The number of = available=20 >scoreboard entries is determined during the configuration phase of the = startup=20 >(it cannot even be changed during graceful starts, this is why we add = some=20 >additional entries to the number of workers we have counted in the = configuration). > >To be honest I am still not convinced that the dynamic creation of = workers is a good idea at all. > I believe I have addressed your concerns in a new patch posted for = PR#43308 in which I introduce a new configuration directive that limits = the number of dynamically created workers. During configuration I also = increment proxy_lb_workers by the value of ProxyMaxAddtlWorkers in order = (at least I hope) for additional scoreboard entries to be allocated... BR -ascs