On Mon, Feb 11, 2013 at 6:00 PM, Amol <[email protected]> wrote: > ok i got the point since the check.txt was an empty file and wasn't > actually doing any specific task on the server, it kept responding with may > be an http 200 message > > so instead if i have a file like check.php which has <?php echo "i"m > healthy"; ?> > then it would run this and wait for the response on every health check > > i think the key as you said is not to have a very taxing health check but > at the same time having something in place instead of a blank file > > my main focus to solve is when apache runs out of memory and exhausts its > stipulated 150 processes, then the next connection to that server for php > request would timeout..hence i am not looking at making db connection from > all server for every single health check..is that correct thought? >
Yes, for just checking Apache, that would be better. You might also want to investigate the http_check_disable_on_404 directive http://code.google.com/p/haproxy-docs/wiki/http_check_disable_on_404
