I suggest you ...

Change Load Balancer hash algorithm for 2- and 3-tuple hashes

It appears that Load Balancer uses the same algorithm to calculate hashes for 2-, 3- and 5-tuple hashes. This way for 2- and 3-tuple hashes there is simply less input variables and source IP addresses from the same subnet receive the same hash value. With the same hash these clients get connected to the same node in the Load Balancer making very unbalanced load (in my case typical load distribution across 2-node LB is 90/10).

I suggest to change hash algorithm for 2- and 3-tuple hashes so it produces different hash values.

6 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Alex Osipov shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base