least-connections-member and least-connections-node

Least connections member can be viewed as sorting a list of pool members in a pool by the number of open connections (tcp/udp/etc.).

I would look at using least connections member mostly, but if you have a machine that takes the same type of data on multiple ports, say a server that hosts web sites different ports (say tcp/8000-8019), and each port is associated with a virtual server with pools referencing only 1 port, then least connections node on all of those pools may make sense.