Download Latest Version
v1.8.222.zip (5.3 MB)
Get an email when there's a new version of Marathon
| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2019-04-08 | 1.5 kB | |
| v1.5.15.tar.gz | 2019-04-08 | 4.3 MB | |
| v1.5.15.zip | 2019-04-08 | 4.9 MB | |
| Totals: 3 Items | 9.2 MB | 0 | |
Introduce global throttling to Marathon health checks
Marathon health checks is a deprecated feature and customers are strongly recommended to switch to Mesos health checks for scalability reasons. However, we've seen a number of issues when an excessive number of Marathon health checks (HTTP and TCP) would overload parts of Marathon. Hence we introduced a new parameter --max_concurrent_marathon_health_checks that defines a maximum number (256 by default) of Marathon health checks (HTTP/S and TCP) that can be executed concurrently in the given moment. Note that setting a big value here and using many services with Marathon health checks will overload Marathon leading to internal timeouts and unstable behavior.
Fixed Issues
- MARATHON-8596 Introduced global throttling to Marathon health checks
- MARATHON-8575 Fixed a broken migration for app definitions with port mappings protocol "tcp,udp" which is no longer valid and should be "udp,tcp"
- MARATHON-8566 Fixed a rare bug where deployment was sometimes not immediately visible through the
v2/deploymentsendpoint after creation
Note: Previous 1.5.14 release introduced a regression where an unhealthy instance would not be killed. This will not happen anymore (promise) and we do not recommend using 1.5.14 release if you use health checks.
