Forum Discussion
ta11ey_89826
Nimbostratus
Oct 30, 2008Need Cookie Hash iRule Help
I have an iRule performing a cookie hash that is working... for the most part.
The pool 'amtrial_http' contains the two nodes referenced in the iRule. Obviously, when the 1st request c...
c_p_i_o_17707
Jan 07, 2009Historic F5 Account
In case of "least connections" algorithm, (as you had first selected) it is possible that the BIG-IP will pick the same member over and over again if all pool members have the same number of connections.
e.g. if pool member A and B both have 0 connections. Assume request 1 will be handled by A. When request 2 comes in, if A is done with request 1, then it is possible that A will also handle request 2 (since A and B are again at 0 conns).
I briefly tried the irule you provided with my machine and for round robin I could see my requests going to both pool members (i'm using version 9.3.1).
Could you add the following event/log statement to your irule?
when SERVER_CONNECTED {
log local0. "[LB::server addr]"
}
This will show the actual pool member selected by big-ip each time after it hits the else clause with the "default" log message in the rule.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects