Weighted load-balancing could not choose the expected node
This issue affects the weighted load-balancing method, which assigns a different "weight" to each node. In some cases it has been noticed that sessions are not assigned to the next node in accordance with its weight.
For example, if there are nodes with sessions in status "disconnected", the load-balancing algorithm could exclude these nodes. As a result, sessions could be concentrated only on one or a few nodes until they go out of resources and prevent new sessions from starting.
