Hey, According to me, it's easier to change the NIC, since your intermittent issues may happen under load only.
With HAProxy, I can't see anything you can currently do to avoid this behavior. I mean that NIC intermittent issues may happen under load, so haproxy would consider server down. load decreasing, NIC will work properly again and haproxy would consider server operational. and so on for a lonnnnnnnnnng time. Don't try to hide a hardware issue using a load-balancer... cheers On Thu, Feb 2, 2012 at 4:28 AM, John Clegg <[email protected]> wrote: > Hi > > I'm trying to understand how ensure backserver which is failing and > classified as dead stays dead. > > I've just had an instance on another server which is using another > load-balancer where the NIC has intermittently failing and it caused the > load-balancer to flap constantly. > > I would like to set a threshold where if the back-end service fails that it > says dead, it stays dead and needs to be manually re-added to > load-balancer. > > I'm trying to understand how the rise and fall settings (plus other config > settings) can achieve this, or if there is another approach. > > Any ideas would be appreciated. > > Regards > > John > > -- > > John Clegg > Dash Tickets > http://www.dashtickets.co.nz >
