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

"Bad gateway" when performing rolling updates of Traefik #92

Open
lawliet89 opened this issue Jul 13, 2018 · 0 comments
Open

"Bad gateway" when performing rolling updates of Traefik #92

lawliet89 opened this issue Jul 13, 2018 · 0 comments
Labels
D-Medium Difficulty Medium P-Medium Priority Medium

Comments

@lawliet89
Copy link
Collaborator

Currently, when Traefik is being upgraded in a rolling manner, there will be a period of time while ELB updates its target groups when end users will get a "bad gateway error".

This is because the Traefik job can potentially be running on less than the maximum number of Nomad clients.

There are two ways to solve this:

  • Run Traefik as a system job. But we must be careful to write a constraint such that only those that are in the ASG that is used as the target group for Traefik's ELB has this scheduled.
  • Run some kind of service that reacts to consul watch changes in the Traefik service and then react accordingly.
@lawliet89 lawliet89 added P-Medium Priority Medium D-Medium Difficulty Medium labels Aug 2, 2018
qbiqing pushed a commit that referenced this issue Mar 10, 2020
@guangie88
Add AWS Elasticsearch as part of infra (#92)
e512681 
* Add AWS Elasticsearch service as part of staging

* Use latest ES version

* Revert bullet point symbol for README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
D-Medium Difficulty Medium P-Medium Priority Medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lawliet89