Skip to content

v1.5.15
Compare
Choose a tag to compare
@zen-dog zen-dog released this 10 Apr 11:18
· 1103 commits to master since this release
v1.5.15
8a92920
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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/deployments endpoint 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.

Assets 2
Loading