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
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
Appears to me that when the configuration is restarted, round robin always goes to the top of the backend list. this would be easier to be sure if the number of active connections didn't disappear on reload.
Even if tracking internal HAPROXY round robin variable is not feasible shuffle backend before reload would even the grounds a little.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Appears to me that when the configuration is restarted, round robin always goes to the top of the backend list. this would be easier to be sure if the number of active connections didn't disappear on reload.
Even if tracking internal HAPROXY round robin variable is not feasible shuffle backend before reload would even the grounds a little.
The text was updated successfully, but these errors were encountered: