You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2014/09/30 08:48:23 UTC

[Bug 57046] New: Add additional parameter to enable check URL before forwarding request to balancer backends

https://issues.apache.org/bugzilla/show_bug.cgi?id=57046

            Bug ID: 57046
           Summary: Add additional parameter to enable check URL before
                    forwarding request to balancer backends
           Product: Apache httpd-2
           Version: 2.4.10
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: mod_proxy
          Assignee: bugs@httpd.apache.org
          Reporter: andre.wendel@bmw.de

Hello,

currently I'm facing a lot of problems in the case of using mod_proxy and
mod_proxy_balancer in an big environment wit lots of backends.

Problem is that if a backend needs to be restarted and comes up (in my case an
glassfish server), immediatly after the restart of the server and after a ping
is accepted by the backend mod_proxy activates the balancer member again and
proxies requests to the backend, even before the web-container is able to
deploy or load the application. Due to the fact that the new backend is not
under load a load of initial request are proxie dto the new backend and will
come back with failures because the web container is not available.

There are some features like configure timeouts to disable the worker for an
amount of minutes until the web-container is completly loaded, but this does
not really satisify my needs, because it's  more like a work around. 

A better solution would be to enable the balancer to first check if the url,
the client requests is available and gives a correct 200 before the apache
proxies the request to the backend. This feature can maybe be activated based
on a balancer-member property i.e. "checkurl=on".

The check could by done everytime, after a configured timeout (like every 60s)
and at least at the point a new balancer-member is recognized before the first
request gets proxied to this backend.

I.e. an additional property like "checktimeout=60", which means the URL-Check
is done every 60 seconds for this URL (0s could mean, before every request).
And as basic feature the URl check is done every time an new balancer-member
has been added for an backend "checkurl" is activated.

Best regards,
André

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org