This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 300
Ability to choose between '-sf' and '-st' HAProxy signal flags #318
Labels
Comments
brndnmtthws
added a commit
that referenced
this issue
Sep 26, 2016
brndnmtthws
added a commit
that referenced
this issue
Sep 26, 2016
brndnmtthws
added a commit
that referenced
this issue
Sep 26, 2016
I'm not opposed to it, but I think I prefer #321. |
I think it will work for me too. |
brndnmtthws
added a commit
that referenced
this issue
Sep 29, 2016
brndnmtthws
added a commit
that referenced
this issue
Sep 29, 2016
brndnmtthws
added a commit
that referenced
this issue
Sep 29, 2016
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
marathon-lb
has the-sf
flag hard-coded. Would you consider making it configurable?I think this will be useful to people running long-lived TCP connections.
Ideally I would add a timeout to the
-sf
flag after which it will fail-over to the-st
behavior. But this is a request for the upstream HAProxy project. What do you think?The text was updated successfully, but these errors were encountered: