Forum Discussion
Asura2006
Altocumulus
AltocumulusPriority group activation and automatically closing connections when higher priorty group goes UP.
Hello we have a configuration where in one pool there are 6 nodes with 2 priority groups of 3 nodes each. 3 nodes with piriority group 1 (backup) 3 nodes with priority group 10 (primary). Priority...
Kai_Wilke
MVP
MVPQuestion to your scenario: Do your application have to maintain a server side session state which require the use of what F5 is calling "Session Persistence", or are your application absolutly fine if request from the same client is per-request load balanced to the available online nodes?
Depending on the requirement of persistence, you would either need to create a GUI based setup via OneConnect (to enable per-request balacing) and Pool- and Monitor-Settings. Or you may end up with a custom iRule to handle the closing of such persistet sessions if your primary/backup systems are failover/fallback.
Cheers, Kai
Asura2006Right now there is no requirement for persistance so i guess we will have to use the OneConnect profile pool and monitor setup? But i don't see how it is going to delete the connections for backup PGA after the priority PGA will become active.
In one connect program there is a maximum Age time but I dont know if I should set it to something like 2-3 minutes. Wouldnt it defeat the purpose of OneConnect profile ?
- Kai_Wilke
One Connect Profile will completely detach the client-side TCP connection from your server-side connections, so that your dont have to care about already established connections. Each incomming client-side HTTP request will be load balanced (based on Pool-Priority-Groups availibilites) and then use a pooled service-side connection to the individial members.
OneConnect enables you to switch between Pool-Priority-Groups without closing the client-side connection, the very next HTTP request will be load-balanced to the Master/Fallack Priority-Group as needed.
If applying a OneConnect Profile to your Virtual Server is not a problem, then you can continue to use your single Pool setup including Priority-Based Activation. The only change needed would be to adjust your Health-Monitors, so that a node will delay a state change to UP for 2 minutes (via "Time Until Up" setting).
Let me know if you need further assitance to get the OneConnect setup running.
Cheers, Kai
Hey Asura2006 - if Kai's response solved your issue, could you please hit the Accept as Solution button, so future users dealing with the same problem can easily find the solution to their issue?
