Forum Discussion
Persistence on value present in one of 3 places
Hello!
Thank you for this. This works really well and logs the value for each of the 3 parts. From the screenshot below you can see the results of this:
Something however wasn't working well and some transactions were failing and this I believe is due to the request not "persisting" and being sent to the other Pool Member. (the setup is testing a round robin accross 2 seprate servers)
I then added the LB_SELECTED LB::SERVER to see exactly where this traffic is going to and it seems as though the logging of LB::SERVER isn't really logging each HTTP request. Each transaction / connection attempts generates multiple requests as you can see from the above yet for some requests the server is only logged once.
I then decided to use BIG IQ and can see that some are being sent to the wrong pool member and I have no idea why. I can see the reference is present in the header or payload and is always there.
Some requests don't even log the Pool Member;
I'm also unable to get the LB::enable_decisionlog working to see the logic behind choosing said pool member.
Hi Gus,
You might need to add an OneConnect profile to evaluate the load balancing decision per request. See this article: https://my.f5.com/manage/s/article/K7964
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