Eric, Our usual advice is that for anything with over 200 health checks (which your configuration sounds like it definitely is) then you should look carefully at your options for simplifying the chec
I've been looking for an alternative to ldirectord because it is single-threaded. My config file is so long that it now takes about 3 or 4 minutes to health-check all my servers, which means a server
Eric, That's great news, glad to hear that it is working! Fudge sounds nice :-). But maybe just spread the word that Loadbalancer.org are nice people? http://loadbalancer.org/blog/so-just-how-should-
Malcom -- My wife makes wonderful fudge at Christmas time. Where should I send yours? Because... ethtool -K p2p1 gro off ethtool -K p2p2 gro off ethtool -K p2p3 gro off ethtool -K p2p4 gro off ...tot
Eric, Ah , OK I thought that might be too simple :-). Some general advice from our end is: We have had problems with both LRO & GRO in the past (we disable them both), and we also run irqbalance (to
That's the odd part. We don't have any WRR health checks at all. Everything is WLC. And the ldirectord.cf file did not change, not did the version of ldirectord itself. I have checked through the fil
Eric, What kind of health checks are you using, it sounds like no backend servers available in the cluster? -- Regards, Malcolm Turnbull. Loadbalancer.org Ltd. Phone: +44 (0)330 1604540 http://www.lo
...oh, and one other thing. After the upgrade, I am now seeing these syslog messages once approximately per second... Sep 18 09:06:26 lb01a kernel: IPVS: WRR: no destination available: no destination
Formerly both of my load balancers were running RHEL 5.2 and everything has been awesome for years. I reformatted them and installed RHEL 6.3 (because that's what's on the rest of my servers) and now