httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mathieu CARBONNEAUX <i...@ch2o.info>
Subject Re: [info@ch2o.info] Re: mod_proxy_balancer/mod_proxy_ajp TODO
Date Wed, 21 Jun 2006 09:41:58 GMT
like alteon load balancer from nortel... they provide health check for many protocole...

for http is only simple get to backend... and on the backend you must provide a responde this
check (ex:statics file)...

you can define how many ping after how it consider the backend dead...
and how many seconds between ping...


  _____  

From: Jim Jagielski [mailto:jim@jaguNET.com]
To: dev@httpd.apache.org
Sent: Mon, 19 Jun 2006 23:02:11 +0200
Subject: [info@ch2o.info] Re: mod_proxy_balancer/mod_proxy_ajp TODO

Ruediger Pluem wrote:
> 
> +1. Just one thought: I think it would be useful to have this 'health check'
>     approach somewhat generic so that we can implement the call to it inside mod_proxy
>     and its connection pooling itself (e.g. with providers supplied by schema
>     handlers / modules). For AJP this would be CPING/CPONG of course and
>     mod_proxy itself could offer a generic TCP connection 'health check' provider that
simply
>     checks the status of a TCP connection as far as this is possible without
>     reading or writing data. This would be a very generic provider. Other protocol
>     handlers could define other (better) protocol specific providers and
>     just plug them in.
> 

Agreed. Making a generic hearbeat interface that could vary depending
on the actual protocol would be v. cool. So for AJP, CPING/CPONG,
for HTTP some sort of generic TRACE (or HEAD)...
-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
     "If you can dodge a wrench, you can dodge a ball."
  
Mime
View raw message