Deploy and manage containers (including Docker) on top of Apache Mesos at scale.
HeartbeatMonitor before Marathon is connected to Mesos.MARATHON_APP_ env vars.Added Metrics, Bug fixes, Backports and performance improvements.
currentDeploymentCount is the current active deployments and DeploymentCount is an always incrementing count of deployments.reviveCount is the count of revives sent to Mesos.launchOperationCount, launchGroupOperationCount, reserveOperationCount provides the count for the launch, launchGroup and reserve operation calls to Mesos.bytesRead, bytesWritten are added to track all API request / responses. (#6197)light param for /v2/events?plan-format=light
containerPort=0 (#6235) (#6240)--max_running_deployments was added to limit the max number of concurrently running deployments (#6178)diff: https://github.com/mesosphere/marathon/compare/v1.5.8...v1.5.9 https://downloads.mesosphere.io/marathon/releases/1.5.9/marathon-1.5.9.tgz
This change introduces the Marathon command line flag gpu_scheduling_behavior
to define how offered GPU resource should be treated.
Valid values are
undefined indicating the old behaviour, ie apps and pods without GPU
requirement might launch on a node with GPU resources. A warning message
will be logged in such cases.restricted indicating that resources on GPU containing nodes should only be
used for applications that require them.unrestricted indicating that resources on GPU containing nodes can be used
whether or not applications require them.The default is undefined.
restricted and unrestricted GPU scheduling behavior (#6052)end field of the /metrics endpoint was not properly populated (#6035)Bugfix release
AuthorizedResource:: SystemConfig type (instead of SystemMetrics) (#6100)Special thanks to @clems4ever and @pierresouchay for all your efforts!
v2/groups request performance: 10x throughput, 5x latency and 5x std. deviation improvement. (#6001)Recommended Mesos version is 1.5.0.
As of 1.6 version, Marathon switched to the new versioning strategy. We mostly follow SemVer but we needed to have a unique version number for every master build. For that reason, first 1.6 public release is 1.6.322. It does not mean there were 321 releases prior to this one that we did not share with the community, the number actually is number of commits on the master branch since the last minor release (so 1.5). As for all future releases, the fix version will be increasing but don't expect the numbers to be consequential.
We have improved the overall performance of serialization in our API by 10x, leading to a substantial reduction in load for requests to /v2/apps, and /v2/groups. #5973
Marathon has simple built-in support for Mesos Maintenance Primitives. For more information please see our docs.
It is now possible to run stateful applications inside pods. For more information, please see docs.
portMappings are exposed as $PORT_NAME variable #5888
The Sentry Raven log appender has been updated to version 8.0.x. Users that have enabled the Sentry Raven appender will need to update their configuration according to the sentry migration guide.
Marathon 1.6.0 is compiled using Scala 2.12. This means that plugins which were compiled using Scala 2.11 will make Marathon fail during startup due to binary incompatibility between Scala 2.11 and 2.12.
The /v2/schema route, and JSON Schema definitions, are deprecated in favor of RAML. They will not be kept up-to-date. The endpoint will be disabled in Marathon 1.7.0 (can be re-enabled via an extended grace-period deprecation flag), and then completely removed in Marathon 1.8.0. The extended grace-deprecation flag will be documented in 1.7.0 and mentioned in the release notes. You can watch MARATHON-7981 for more details.
Marathon Health Checks will continue functioning, but are not actively supported. You should migrate to Mesos Health checks as soon as possible.
In Marathon 1.8.0, we will start logging warning each time an app/pod references a Marathon health check.
In Marathon 1.9.0, if you upgrade and have app definitions with Marathon Health Checks, then Marathon will refuse to start. You will be able to temporarily re-enable them via an extended grace-period flag.
Marathon Health Checks will be completely removed in Marathon 1.10.0, and Marathon will refuse to start if the extended grace-period deprecation flag is specified.
toString for Group and log clashing ids.containerPort as $PORT_NAME in environment variables.https://github.com/mesosphere/marathon/compare/v1.4.10...v1.4.11
https://github.com/mesosphere/marathon/compare/v1.4.9...v1.4.10