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

404 responses when a new Marathon leader is elected #653

Closed
gomes opened this issue Aug 29, 2016 · 1 comment
Closed

404 responses when a new Marathon leader is elected #653

gomes opened this issue Aug 29, 2016 · 1 comment

Comments

@gomes
Copy link
Contributor

gomes commented Aug 29, 2016

The problem: I am running a lot of apps in my Marathon cluster, +200 and when a leader is elected it actually runs healthchecks for all tasks, so it starts with 0 healthchecked apps and starts to check every task and populating data about the results. Meantime, Traefik thinks I don't have my apps anymore, because it assumes if I don't have healthchecks, it's unhealthy. That's untrue, because my apps are still there, Marathon just didn't had enough time to check all of then.

So, Traefik should not consider the absence of a healthcheck the same as not healthy.

@emilevauge emilevauge added the bug label Aug 30, 2016
emilevauge pushed a commit that referenced this issue Sep 14, 2016
Healthcheck are not mandatory, so if a result is not present, assume it
is ok to continue. Fixes the case when a new leader is elected and
don't have any healthcheck result's, returning 404 to all requests.
#653
@gomes
Copy link
Contributor Author

gomes commented Nov 21, 2016

The PR (#665) fixing this issue was merged in version 1.1.0, so I will close this issue.

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

No branches or pull requests

5 participants