Forum Discussion
littlebunny
Nimbostratus
May 22, 2019LTM virtual pool activation priority behaviour (v14.0.0.3)
Hello
We had an issue where monitoring for one of our pool members dropped very briefly (a few seconds) and when it came back up all of the traffic was still going to the other node. Before the node dropped all traffic was going to it, how is priority supposed to behave in this scenario? Should traffic have switched back over to the higher priority node once it came back up?
Thanks
LB
2 Replies
- SurgeonRet. Employee
- Every pool has "Slow Ramp Time" setting, It tells how log big-ip should send less traffic to a member the become online..
- If you have persistence profile then expect uneven load balancing until persistence records expire.
- littlebunny
Nimbostratus
Thanks, we do have a persistence profile in place and the expiry time is set to 8 hours so that would explain it!
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
