GTM load balancing issue

Is it lopsided in the number of connections reported to the 443 VSs or lopsided in the answers the GTM gives out for that wideip? Those are very different issues.

There may very well be a corresponding difference in the connection statistics going to these 443 VSs versus the port 80 VSs.

Perhaps log some connection info on the sets of VSs. You might see a few long duration connections on the 443 that happen to get assigned to one VS might cause a lot more short duration connections to be assigned to the other VS. This could affect the pattern of IPs being returned by the GTM for your wideip as well as the number of connections being reported by the LTM for the VS.

I can think of several, but the answers may not necessarily be correct.

The least-connections is usually correct in its processing. However it's least CONCURRENT connections at the time of the LB selection. It's possible that the :443 and :80 connections take different amount of time to complete a connection, which could be skewing the results between them.

Is it also possible you're selecting by node for one and member for the other? Or one of the nodes has additional connections from another pool (And you're selecting node and not member least connections)

H

Yes, lopsided in the answers the GTM gives out for that wideip.

I should have provided more information. The requests are coming from a load generator, which is sending the requests via https (it never changes to http). If we remove the port 443 pool members and add the port 80 pool members in the middle of testing the requests even out between the pool members. In theory the requests should obtain an IP from the GTM and then head straight to the port 443 VSs on the LTMs. Trying to figure out why it even matters what port the GTM pool members are using. Ah ha! The GTM is monitoring the port 80 VSs on the LTM, which should have no traffic/connections. Hmmmm, what does Least Connections do when there are zero connections?

Mmm... Think it will do in order as least connections implies NOW not what happened earlier...

But worth asking support to confirm.

That was indeed the case. The GTM was monitoring the port 80 VSs on the LTMs while all the traffic was going to the port 443 VSs. Please close this silly ticket :)