Forum Discussion
AltocumulusFlip-flop load balancing
AltocumulusNo. All traffic should go to a single pool member (Node1). If that pool member becomes unavailable, traffic goes to the other pool member (Node2), and continues to go to this pool member (Node2) regardless of the state of the other pool member (Node1).
Traffic will continue to go to Node2 until it becomes unavailable, then traffic goes to Node1 and continues to go to this node regardless of the state of Node2.
and so on, and so on....
The theory is the server admins can do whatever they want with the node currently not receiving traffic without fear of it unexpectedly taking on traffic from the virtual server.
It is possible with universal persistence and a simple iRule.
when CLIENT_ACCEPTED {
persist uie 1
}
K000140287: Direct traffic to only a single node in a pool at a time using Single Node Persistence
https://my.f5.com/manage/s/article/K000140287
