point to different Pools w/ different persistence

Question

I have the following iRule configured, but each pool needs to use a different Persistence Profile.  How can I accomplish this?&nbsp;
&nbsp;when HTTP_REQUEST {
&nbsp;if {[HTTP::uri] starts_with "/member"}
&nbsp;{ pool POOL_A }
&nbsp;else { pool POOL_B }
&nbsp;}&nbsp;
&nbsp;Thank you!

jrahm · Answer

when HTTP_REQUEST {
  if { [HTTP::uri] starts_with "/member" } {
    pool POOL_A
    persist xxx
 } else { 
    pool POOL_B
    persist yyy
    }
}

greg_burch · Answer

I'm attempting to do the same thing, but it doesn't seem to be working reliably at all.  The following iRule is specified within a persistence profile that is assigned as the Default Persistence Profile of a virtual server (logging statements were added for debugging purposes):&nbsp;
&nbsp;when HTTP_REQUEST {
&nbsp;   if {[string tolower [HTTP::uri]] contains "tcgiservlet" } {
&nbsp;    persist source_addr 255.255.255.255 120
&nbsp;    log local0. " [IP::client_addr] - [HTTP::uri] - SOURCE persistence selected "
&nbsp;   } else {
&nbsp;    persist none
&nbsp;    log local0. " [IP::client_addr] - [HTTP::uri] - NO persistence selected"
&nbsp;   }
&nbsp;}&nbsp;
&nbsp;when LB_SELECTED {
&nbsp;  log local0. " [IP::client_addr] - [HTTP::uri] - to node [LB::server]" 
&nbsp;}&nbsp;
&nbsp;______________________________________
&nbsp;A sample of the logging that is produced is as follows:&nbsp;
&nbsp;Feb 22 14:07:38 tmm tmm[1036]: Rule XXXXXXXX_PERSIST :  y.y.y.y - /live/servlet/GetLeastLoadedComponent?xxxxxx - NO persistence selected
&nbsp;Feb 22 14:07:38 tmm tmm[1036]: Rule XXXXXXXX_PERSIST :  y.y.y.y - /live/servlet/GetLeastLoadedComponent?xxxxxx - to node POOLNAME-80 z.z.z.z 80
&nbsp;Feb 22 14:07:38 tmm tmm[1036]: Rule XXXXXXXX_PERSIST :  y.y.y.y - /live/servlet/tcgiServlet - SOURCE persistence selected
&nbsp;Feb 22 14:07:38 tmm tmm[1036]: Rule XXXXXXXX_PERSIST :  y.y.y.y - /live/servlet/tcgiServlet - SOURCE persistence selected
&nbsp;Feb 22 14:07:39 tmm tmm[1036]: Rule XXXXXXXX_PERSIST :  y.y.y.y - /live/servlet/tcgiServlet - SOURCE persistence selected
&nbsp;Feb 22 14:07:39 tmm tmm[1036]: Rule XXXXXXXX_PERSIST :  y.y.y.y - /live/servlet/tcgiServlet - to node POOLNAME-80 167.z.z.z 80&nbsp;
&nbsp;The problem is that the persistence doesn't seem to be taking effect immediately, as there will be several requests to one back-end node, and then all subsequent requests will go to the other back-end node.  One thing I especially don't understand is the LB_SELECTED event only seems to trigger sporadically, and there doesn't seem to be any rhyme or reason to it.  It doesn't occur for every request, but it occurs much more often than 120 seconds, which is the timeout value of the persistence.&nbsp;
&nbsp;Has anyone seen behavior like this or shed any light on what might be happening?&nbsp;

unruley_95363 · Answer

That's classic non-OneConnect behavior.  The LB_SELECTED event is only fired when a load-balancing decision is made.  And of course, persistence only plays a factor when the load-balancing decision is made.&nbsp;
&nbsp;As a side effect of OneConnect, load-balancing will occur on every request.  However, without OneConnect, load-balancing only occurs when the pool changes.  Any subsequent requests that happen to go to the same pool will stay connected to the last pool member.&nbsp;
&nbsp;So, you have two ways you can change this behavior: 1) Add OneConnect; 2) at the beginning of HTTP_REQUEST call LB::detach.&nbsp;
&nbsp;HTH

Forum Discussion

point to different Pools w/ different persistence

3 Replies

AppWorld Berlin iRules Contest!

F5 AppWorld 2026 Las Vegas - iRules Contest Winners!

Recent Discussions

SSL Forward Proxy, iRules and Client Hello

monitor/healthcheck issue with envoy gateway

Recommendation for Adv. Lab

Changes to DO and AS3 GitHub - no longer monitored

How to Verify config before loading to F5

Related Content

Persistent and Persistence, What's the Difference?

F5 XC – Persistence and Resiliency pt. I (persistence)

Copper SFP Differences

Http monitor on different port

Difference between Ratio and Ratio Least Connection Load Balancing Method