On Thu, Aug 28, 2014 at 10:31 PM, Rainer Duffner <[email protected]> wrote: > Hi, > > > we will put haproxy in front of a Zimbra infrastructure (which we have > split-up, so that there is a "front end", with pop, imap, smtp and a "back > end", where the mail sits). > > I have too haproxy-servers (active/standby via CARP) that are checking the > front-ends. > I check: > - smtp > - smtps > - submit > - pop + pops > - imap + imaps > > from both haproxy-servers simultaneously. > > If I use the default check frequency, it just bombards the servers with > requests that often can't even finish in the time it takes to launch the next > check. > If I increase the check-frequency too much, it will take longer to take a > server out of the pool in case of failure - and checks still don't > "balance-out" (or do they?). > But they are all more or less connected: if one of them fails, it's highly > likely that all the others will fail, too. > > So, ideally, I'd like to have something like this: > - check service A (maybe POP3) > - wait maybe 30s > - than check the next service (e.g. POP3S). > - if one fails, remove that backend-server from the pool for all services > - alternatively, instead of doing the above, re-schedule the checks so the > next check happens immediately > > > Does that sound insane? > ;-)
Hi, maybe you could share your HAProxy configuration :) By default, HAProxy tests a service every 3s, which is fine. It just does a tcp connect, so nothing complicated for your server to handle. Can you confirm that if POP fails on a server, it means that IMAP and SMTP will fail too? (this is what I'm understanding from your mail above). Baptiste
