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.

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

Adding check of alive status to haproxy.conf #990

Merged
merged 1 commit into from
Jun 30, 2016
Merged

Adding check of alive status to haproxy.conf #990

merged 1 commit into from
Jun 30, 2016

Conversation

nsdavidson
Copy link

The current implementation does not remove dead nodes from its config. This causes timeouts if
backend nodes go away. It can also lead to config conflicts if new nodes come up with the same IP
as stale node entries.

This change allows nodes to be removed from haproxy when they are deemed no longer alive by the supervisor.

Signed-off-by: Nolan Davidson [email protected]

The current implementation does not remove dead nodes from its config.  This causes timeouts if
backend nodes go away. It can also lead to config conflicts if new nodes come up with the same IP
as stale node entries.

This change allows nodes to be removed from haproxy when they are deemed no longer alive by the supervisor.

Signed-off-by: Nolan Davidson <[email protected]>
@thesentinels
Copy link
Contributor

By analyzing the blame information on this pull request, we identified @kevindickerson and @adamhjk to be potential reviewers

@bookshelfdave
Copy link
Contributor

@thesentinels delegate=nsdavidson

I'm delegating merge access to you, please read these instructions for more info!

@nsdavidson
Copy link
Author

@thesentinels r+

@thesentinels
Copy link
Contributor

📌 Commit 8a3424d has been approved by nsdavidson

@thesentinels
Copy link
Contributor

⌛ Testing commit 8a3424d with merge 93e0509...

thesentinels added a commit that referenced this pull request Jun 30, 2016
Adding check of `alive` status to haproxy.conf

The current implementation does not remove dead nodes from its config.  This causes timeouts if
backend nodes go away. It can also lead to config conflicts if new nodes come up with the same IP
as stale node entries.

This change allows nodes to be removed from haproxy when they are deemed no longer alive by the supervisor.

Signed-off-by: Nolan Davidson <[email protected]>
@thesentinels
Copy link
Contributor

☀️ Test successful - travis

@thesentinels thesentinels merged commit 8a3424d into habitat-sh:master Jun 30, 2016
@smith
Copy link
Contributor

smith commented Jun 30, 2016

Built and uploaded to depot https://app.habitat.sh/#/pkgs/core/haproxy/1.6.5/20160630143421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants