Forum Discussion
7 Replies
- Dylan_375544Cirrocumulus
Well, I labbed out your situation and I have the same issue. It seems as if "least connections" takes precedence over "ratio".
As soon as I changed my LB method to "Ratio (member)" the LB acted properly and heeded my ratios.
As soon as I change it back to "Ratio Least Connections (Member)" it goes back to 50/50 between my two vips.
My only advice would be to change your LB method to just "Ratio (member)"
(my lab version was 13.1.1.3)
-Dylan
- Leon_Xu_378103Nimbostratus
Thanks Dylan!
"Ratio (member)" works.
For "Ratio Least Connection (Member)" mode, my understanding is "ratio" should take precedence over "least connections", but obviously it isn't. I'm wondering if this is a bug in V13. Not sure if other versions having this problem.
- Raman_KaushikRet. Employee
Try this:
- Keep 2 pool members active.
- Give ratio is 10 and 30. (basically 1:3)
- Reset the stats.
- curl -v -k [1-1000]<<<<<<<<<<<<
- The curl command will generate 1000 requests, however current connection would be just 4 on bigIP.
- Check the stats again.
Worked for me.
- Leon_Xu_378103Nimbostratus
Thanks Raman. It worked for me as well!
- Raman_Kaushik_3Historic F5 Account
Try this:
- Keep 2 pool members active.
- Give ratio is 10 and 30. (basically 1:3)
- Reset the stats.
- curl -v -k [1-1000]<<<<<<<<<<<<
- The curl command will generate 1000 requests, however current connection would be just 4 on bigIP.
- Check the stats again.
Worked for me.
- Leon_Xu_378103Nimbostratus
Thanks Raman. It worked for me as well!
- Stanislas_Piro2Cumulonimbus
I never played with ratio least connection member algorithm, but it seems it is like that:
It evaluate number of connection * member ratio, then do the same as least connection
If you do tests with only one curl, when the request is ended, connection closes, so number of connection for each member equals 0
Least connection algorithm do round robin on all member matching same connection number