Forum Discussion
dragonflymr
Cirrostratus
Feb 12, 2015Fastest LB, OneConnect and...
Hi,
I am a bit lost when it comes to terms used for Fastest LB description. Basically it described as based on outstanding L7 requests. But what exactly is that mean? If we talking about HTTP L7...
Brad_Parker
Cirrus
Feb 12, 2015Yes, you should expect that it will count each request when you have a OneConnect profile in use because that decision is being made before a tcp connection is made to the node to send such request.
- Brad_ParkerFeb 12, 2015
Cirrus
This is why it is always recommended to use OneConnect if you are planning on using L7 persistence type such as cookie. - dragonflymrFeb 12, 2015
Cirrostratus
It's recommended because over OneConnect request with different cookies can be directed to different members on request by request basis? So to summarize, when Fastest is used: 1. Without OneConnect outstanding counter is increased when first request is send over TCP connection, following request over the same connection are ignored. Then it means that counter is decreased when last reply is send and TCP connection is closed - so actually it's more like TCP connection counter not request counter - Am I right? 2. With OneConnect counter is increased for each request transmitted over TCP connection and decreased wen each response is received meaning we can have one TCP connection to the server but 5 outstanding request? Piotr - Brad_ParkerFeb 12, 2015
Cirrus
Recommend because only the first request would be guaranteed to persist properly, it would be possible the persistence could be ignored for subsequent requests. 1. I believe the behavior will load balance each request not each connection, that's why it requires the L7 profile(HTTP). It will default back to least connection behavior if you don't have that L7 profile. 2. Yes. Summation, OneConnect shouldn't come into play with this load balancing method. I didn't give enough consideration to all your question in my original response. - dragonflymrFeb 13, 2015
Cirrostratus
Hi, So you mean that even without OneConnect Fastest is counting all request and replies inside TCP connection. Only difference is in granularity that Fastest can achieve in LB: 1. Without OneConnect Fastest is making decision when new connection arrives (based on outstanding request counter) for first request and creates server side connection to the server with lowest counter. If further request are send over the same connection counter is increased (and decreased when there is response) but connection is still glued to the same server - Fastest can't re balance it even if there are members with much lower counter. 2. With OneConnect Fastest is directing connection for first request to server with lowest counter. Then client side and server side connection relation is broken. When next request arrives over the same client side connection it can be directed to another server (one that at given time has lowest counter). Did I get is right? Piotr
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