Hi Laura,
The algorithm is comparable, but there is one big difference. When using the
priority balancing, you will always go back to the highest priority server. In
my case, the algorithm will remain on the active backend as long as it is up,
no matter priority or order in the farm.
Concerning the build from source, I do not have performance issues with pen,
but with pound. And I see that there is a difference in version compared to the
stock Debian version (2.6). Was there a specific reason for this, or is it just
not yet tested with 2.6?
I was trying to build Pound from source using 2.5, but it seams hard to find
the source.... Can you help me out finding it somewhere?
Thank you, Steven.
Steven Van Loo
Lead Security Architect
TrueGEN
Securing your network
T: +32 3 613 23 05
M: +32 475 41 36 55
-----Original message-----
To:[email protected];
From:Laura Garcia <[email protected]>
Sent:Thu 27-02-2014 18:03
Subject:Re: [Zenloadbalancer-support] Feature improvement
Attachment:inline.txt,inline.txt
Thank you for your improvement!
Maybe your lb method is similar to the priority algorithm, isn't it?
Regarding to the pen core, the compilation was done without any specific
configuration or change. And the pen lb core is going to be deprecated as it
could be used the L4 farm instead.
One of the lb methods that we're working on is the implementation of the least
connections, very useful for the vast majority of platforms.
Anyway, thanks a lot for your work!
On Tue, Feb 25, 2014 at 5:06 PM, Steven Van Loo <[email protected]>
wrote:
Dear,
I have implemented Zen loadbalancer v3.0.3 recently and am very happy about the
structure and options available in Zen. Also the performance is very good.
I have however added a new balancing algorithm to the PEN and POUND daemon's to
leverage the following functionality:
Let's say there are 2 backend servers (not limited to 2, but to keep the
example easy).
Both servers are active.
Zen will select server 1 as first selection and will remain on this one as long
as it is active.
When it is not active, the first next active backend will be selected and will
remain on this one as long as this one is active.
Even if server 1 comes back up, it will stay on the selected backend until it
fails. This is independant of the configured priority or weight.
I call it sticky server or backend. The idea behind it is that a server is
active untill brought down and is then available for development until
everything is tested offline (or directly without LB). Once all is ok, the
other one is stopped and all connections are switched to the new version.
I have succesfully implemented this for the pen daemon and the ZEN web
frontend. But for pound, I use pound 2.6 and this gives me performance issues
that I do not have when using the pound daemon that comes with your
appliance/ISO.
Can you tell me why you still use 2.5 and how it is compiled? Did you use
specific build options/libraries. I have installed the Google lib's and
performance add-ons as found in the FAQ, but am not able to have the same
performance, independant of the changes I did.
I attached the diff files for all related files.
Thank you for your help in this.
And let me know if you find this a good option to include in new releases? I
would be very happy.
Kind regards, Steven.
Steven Van Loo
Lead Security Architect
---
TrueGEN
Bredastraat 118/1
2060 Antwerpen
E: [email protected]
T: +32 3 613 23 05
M: +32 475 41 36 55
W: www.truegen.be
Support E: [email protected]
Support T: +32 3 613 23 03
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
