Marathon Files

Changes from 1.8.194 to 1.8.218

Revive and Suppress Refactoring

The revive and suppress logic was unified. In the past Marathon would keep reviving when an instance with a reservation was expunged (case 1) or it would revive when instance should be started (case 2). When no instance should be started Marathon would suppress offers which could conflict with case 1. With the refactoring only one logic decides whether to revive or suppress and thus avoids the conflict. The change also required changing the default --min_revive_offers_interval to thirty seconds. This should avoid overriding revive calls with a suppress too quickly. The --[disable]_suppress_offers flag can switch off suppress calls all together. This should be used when Marathon fails to clean up reservation which requires offers being sent.

Fixed issues

• DCOS-54927 - Fixed an issue where two independent deployments could interfere with each other resulting in too many tasks launched and/or possibly a stuck deployment.

Changes from 1.8.180 to 1.8.194

Fixed issues

• DCOS_OSS-5212 - Fixed an issue that prevented reserved instances created by older Marathon versions from being restarted

• MARATHON-8623 - Fixed an issue that could cause /v2/deployments to become stale

• MARATHON-8624 - Fixed issue where the presence of a TASK_UNKNOWN status could cause an API failure

• DCOS-51375 - Fixed an issue where deployment cancellation could leak instances.

• DCOS_OSS-5211 - The initial support for volume profiles would match disk resources with a profile, even if no profile was required. This behavior has been adjusted so that disk resources with profiles are only used when those profiles are required, and are not used if the service for which we are matching offers does not require a disk with that profile.

• MARATHON-8631 - In order to prepare for the general availability of the DC/OS Storage Service (DSS), Marathon will now default to disk type Mount, if a persistent volume profileName is configured by the user without specifying the wanted disk type. Services like DSS will populate this field to allow users selecting the volumes they previously created. Mesos Root disks will not have a profileName set, so the default for persistent volumes that do not specify a profileName is still Root.

• MARATHON-8422 - Kill unreachable tasks that came back. Marathon could get stuck waiting for terminal events but not issue a kill.