Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Router: Restarting the haproxy router still dispatches connections to a downed backend #4437

Closed
ramr opened this issue Aug 31, 2015 · 1 comment
Closed

Router: Restarting the haproxy router still dispatches connections to a downed backend #4437

ramr opened this issue Aug 31, 2015 · 1 comment
Labels
component/routing priority/P1

Comments

@ramr
Copy link
Contributor

ramr commented Aug 31, 2015

Related to kubernetes/kubernetes#13364

When the haproxy router is gracefully restarted and an endpoint is present but down (see above k8s issue), haproxy will still dispatch connections to the downed backend.

Solution: Check if option redispatch would help.
ramr added a commit to ramr/origin that referenced this issue Sep 1, 2015
@ramr
Fix for issue openshift#4437 - restarting the haproxy router still di…
16c9e6a 
…spatches

connections to a downed backend.
@ramr
Copy link
Contributor Author

ramr commented Sep 4, 2015

Closing this out - fixes in merged PR #4453

@ramr ramr closed this as completed Sep 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/routing priority/P1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ramr @smarterclayton