Hi everyone. I'm testing our shiny new Zen loadbalancer, and in my initial testing it doesn't appear to be sharing the load between workers at all - it only redirects these connections to a single server at a time. This initial testing only involves a single client connecting at once, so I'm hoping that the load will be shared more evenly when there's many connections coming in? This phenomenon happens regardless of what load balance algorithm I'm using, and I've tried them all.
Failover seems to be working flawlessly (and that's really the reason we're making this work in the first place, so I'm happy with that) although in my tests I've found that setting one server into maintenance mode is the only way to actually switch which server gets used. After I un-set maintenance mode on that server however, the server that got failed over to is now the only one getting connections. It's like it won't send connections to the server that was in maintenance mode until I set the *other* server into maintenance mode. Oops! I seem to have stumbled on the bug while I was rubber-ducking with you guys. This problem goes away when I uncheck "Enable client ip address persistence through memory". It seems to set the algorithm to "Sticky client" so long as that checkbox is set, regardless of what algorithm is set in the first place. So here's hoping I've helped in debugging, and maybe someone else will find this post helpful. :) ------------------------------------------------------------------------------ _______________________________________________ Zenloadbalancer-support mailing list Zenloadbalancer-support@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
