Forum Discussion
LB:reselect + persistence
Hello,
I want to create an irule allowing re-select (LB: reselect) a new member of a pool when the member from which are made the connection becomes unavailable. knowing that connections are persistent (universal persist). What is the impact of persistence on the reselection? Can I redistribute the already persistent connections or all persistent connections will be automatically deleted from persist table if the member becomes unavailable?
Thank you in advance for your help.
3 Replies
- What_Lies_Bene1
Cirrostratus
See here for some guidance on your iRule requirement and using the 'Action on Service Down' Pool level feature (which I'd prefer myself): http://support.f5.com/kb/en-us/solutions/public/10000/600/sol10640.html.
Persistence (or rather state) is lost, as a new Pool Member is chosen but will be recreated once the new Pool Member is selected. Assuming you're persisting because of authentication, expect some users to have to reauthenticate. How many will depend on your Pool size.
- Aniissa_5245
Nimbostratus
thank you very much for your answer,
well,
you have an idea on how I can redirect clients were connecting to the server unavailable and redirect to another server with the lb: reselect?
how can I retrieve all the Ips customers who were connecting to that server and redirect them to a new server available?
thanks
- What_Lies_Bene1
Cirrostratus
If you use an iRule or the Action on Service Down feature, it'll all be automatic. There is an example iRule in the link I posted before. No need for collecting IPs or anything manual.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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