You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when consistent hashing is used for load balancing, the server picked by different HAProxy instances can be different, making consistent hashing ineffective.
There should be a way to set a unique id to server when consistent hashing is enabled (http://docs.haproxy.org/2.8/configuration.html#5.2-id). The id can be based on a stable property of the pod (e.g. name, IP, or UID). Using the IPv4 address is probably the easiest, otherwise can hash the value and truncate it to 32 bits.
The text was updated successfully, but these errors were encountered:
Currently, when consistent hashing is used for load balancing, the server picked by different HAProxy instances can be different, making consistent hashing ineffective.
There should be a way to set a unique
id
toserver
when consistent hashing is enabled (http://docs.haproxy.org/2.8/configuration.html#5.2-id). Theid
can be based on a stable property of the pod (e.g. name, IP, or UID). Using the IPv4 address is probably the easiest, otherwise can hash the value and truncate it to 32 bits.The text was updated successfully, but these errors were encountered: