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.
I've been investigating a situation where our MLB docker containers are winding up with multiple HAProxy instances running at 100% CPU (similar to #359). It appears that there's an active connection to one of our Marathon apps that just doesn't go away. I'm tracking that separately, but I was wondering if there was a way to forcibly kill old HAProxy instances anymore. I saw that there used to be one (#321) but that went away in MLB 1.5.0 with #390.
I know that I need to address the underlying issue with why there are these long-running connections but I wanted to know if there's an officially supported way now to force kill old haproxy instances after a reload.
Thanks,
Scott
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.
Hello,
I've been investigating a situation where our MLB docker containers are winding up with multiple HAProxy instances running at 100% CPU (similar to #359). It appears that there's an active connection to one of our Marathon apps that just doesn't go away. I'm tracking that separately, but I was wondering if there was a way to forcibly kill old HAProxy instances anymore. I saw that there used to be one (#321) but that went away in MLB 1.5.0 with #390.
I know that I need to address the underlying issue with why there are these long-running connections but I wanted to know if there's an officially supported way now to force kill old haproxy instances after a reload.
Thanks,
Scott
The text was updated successfully, but these errors were encountered: