RE: take servers out of the pool

From: John Lauro <john.lauro#covenanteyes.com>
Date: Thu, 20 Aug 2009 06:13:48 -0400


I don't think you can easily have two health checks. You could also do port forwarding with iptables or inetd/xinetd and run the health check on a different port. Stop the forwarding when you want maintenance mode.

> -----Original Message-----
> From: Matt [mailto:mattmoran76#gmail.com]
> Sent: Thursday, August 20, 2009 4:23 AM
> To: haproxy#formilux.org
> Subject: Re: take servers out of the pool
>
> In this case I am not load balancing to apache or anything else where
> I can touch/remove a file, I am load balancing directly to the http
> application which doesn't serve any local files, it's a jetty app.
>
> On LVS I could touch a file on the LB or use the ipvsadm command to
> drop a servers weight to 0. However i'm working in EC2 hence my use
> of haproxy.
>
> Could I run apache on the LB and have two health checks? one for a uri
> on the backend ( option httpchk server1/myapp ) and another with
> disable-on-404 that's pointing to a file on the LB (localhost/server1)
> for maintenance?
>
> Thanks,
>
> Matt
>
> 2009/8/20 Willy Tarreau <w#1wt.eu>:
> > On Wed, Aug 19, 2009 at 11:18:08PM +0200, Magnus Hansen wrote:
> >> Very true...
> >> There are some nice examples in the docs.
> >> You could also use the persist option to keep old users on the
> server
> >> while new ones go to other servers.
> >> I use that to make sure i dont kick users..
> >
> > better use the "http-check disable-on-404" now, as it allows you to
> set
> > a server's weight to zero based on a reply to a health-check. If I
> can
> > find some time (joke) I'll update the architecture manual with
> examples
> > using this, and possibly with simple scripts to move a file on the
> server
> > to perform various maintenance operations.
> >
> > Willy
> >
> >
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.392 / Virus Database: 270.13.58/2309 - Release Date:
> 08/17/09 06:08:00
Received on 2009/08/20 12:13

This archive was generated by hypermail 2.2.0 : 2009/08/20 12:30 CEST