Skip to content

Marathon 1.5.12
Compare
Choose a tag to compare
@meichstedt meichstedt released this 02 Nov 21:27
· 1103 commits to master since this release
v1.5.12
4355177

Changes from 1.5.11 to 1.5.12

Default for "kill_retry_timeout" was increased to 30 seconds

Sending frequent kill requests to an agent can in certain cases lead to overloading the Docker daemon (if the tasks are docker containers run by the Docker containerizer). Thirty seconds seems to be a more sensible default here.

Marathon framework ID generation is now very conservative

Previously, Marathon would automatically request a new framework ID from Mesos if the old one was marked as torn down in Mesos, or if the framework ID record was removed from Zookeeper. This has led to more trouble than it has helped. The new behavior is:

  • If Marathon's framework ID has been torn down in Mesos, or if the failover timeout has been exceeded, Marathon will crash, on launch, with a clear message.

  • If Marathon's framework ID record was deleted from Zookeeper or is otherwise inaccessible, and there are instances defined, Marathon will refuse to create a new Framework ID and crash.

For more information, refer to the framework id docs page.

Docker image now allows user nobody

Previously, the Marathon Docker container would only run as user root. The packaging has been updated so that the container can be run as the user nobody. The default user for running the container (and, subsequently, the default value for --mesos_user) has not been changed.

Docker image upgraded to Debian Stretch

The Docker image for Marathon now uses Debian Stretch as a base OS, since Debian Jessie is no longer receiving security updates.

Native Packages

We have stopped publishing native packages for operating system versions that are past their end-of-life:

  • Ubuntu Yakkety
  • Ubuntu Wily
  • Ubuntu Vivid

Additionally, we have added support for Debian Stretch.

Fixed Issues

  • MARATHON-7568 We now redact any Zookeeper credentials from the /v2/info response endpoint.
  • MARATHON-8413 Fixed a bug where versions feature did not work if Marathon was launched using Java 9.
  • MARATHON-8095 Fixed a bug where proxying the PATCH call was impossible due to Java limitations.
  • MARATHON-8430 Readiness checks now work with self-signed certificates.
  • Updated version of Marathon UI to 1.3.1:
    • MARATHON-8255 Marathon UI properly shows fetch URLs in the edit dialog, now.
  • MARATHON-7941 Default for unreachable strategy on PUT /apps now matches POST requests.
  • MARATHON-8084 Fix issue in which POST /v2/apps/{app_id}/restart would not proxy properly.
  • MARATHON-7390 Fix issue in which Marathon would become unresponsive for a long time if Zookeeper DNS cannot be resolved at launch.
  • Fixed a data migration issue in which UNIQUE constraint value was stripped when empty.
Assets 2