homelab/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

refactor: re-organize doc.

Browse source
This commit is contained in:
Fernandez Ludovic 2017-09-01 20:04:41 +02:00 • committed by Traefiker
parent 425b53585a
commit e075dfe911
3 changed files with 80 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/user-guide/marathon.md
View file

@ -50,7 +50,7 @@ Beginning with version 1.4, Traefik respects readiness check results if the Trae
Note that due to the way readiness check results are currently exposed by the Marathon API, ready tasks may be taken into rotation with a small delay.
It is on the order of one readiness check timeout interval (as configured on the application specifiation) and guarantees that non-ready tasks do not receive traffic prematurely.
If readiness checks are not possible, a current mitigation strategy is to enable [retries](https://docs.traefik.io/toml/#retry-configuration) and make sure that a sufficient number of healthy application tasks exist so that one retry will likely hit one of those.
If readiness checks are not possible, a current mitigation strategy is to enable [retries](/configuration/commons#retry-configuration) and make sure that a sufficient number of healthy application tasks exist so that one retry will likely hit one of those.
Apart from its probabilistic nature, the workaround comes at the price of increased latency.
### Shutdown