-
Notifications
You must be signed in to change notification settings - Fork 142
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
What's going on when the restart traefik instance on dcos? #363
Comments
Hi! In order to get community help with this would you mind posting on either the users mailing list users@dcos.io or Slack at chat.dcos.io? I don't know too much about Traefik but you might find someone there who does 🙂 |
@deric ^ |
@hbceylan Which Traefik package version do you use? In the latest version there's a healthcheck configured on "healthChecks": [
{
"gracePeriodSeconds": 20,
"intervalSeconds": 5,
"maxConsecutiveFailures": 2,
"portIndex": 0,
"timeoutSeconds": 2,
"delaySeconds": 15,
"protocol": "MESOS_HTTP",
"path": "/ping"
}
], in your case it appears that port "portIndex": 1, or reorder ports, so that healthchecks will pass (check error log). Also when you use: "upgradeStrategy": {
"minimumHealthCapacity": 0.5
}, it means that you'll need at least 2 public nodes, because you're allocating fixed ports |
What's going on when the restart traefik instances on dcos? Our microservices are unreachable? Yes! How can I handle this?
The text was updated successfully, but these errors were encountered: