Releases: criteo-forks/marathon
Releases · criteo-forks/marathon
v1.9.109-shield-rc2
Added authorization GET /shield - only authentication PUT /shield/<task> - requires UpdateRunSpec of specified task DELETE /shield/<task> - requires UpdateRunSpec if the application exists. If there's no application delete is allowed (to be able to cleanup shields of stale apps using API)
v1.9.109-shield-rc1
Implemented persistence of the shields TODO: - authorization
v1.9.109-criteo11-rc1
To be reverted: Adding new logs to understand MESOS-4345 issue Usage of Map may look strange but could be useful in case we want to add even more logs, keeping history of previous lock versions. * change debug->info to some logs * add reason about why lock was taken * log when re-entering lock with newer version
v1.9.109-criteo11
Always kill oldest instances first (#35) Right now the order of task killing is "unhealthy" first. For very big applications, killing unhealthy and then oldest tasks first is a good heuristic. It favors killing first the instances that may have have leaked. Of course, we could find arguments for sorting in reverse (oldest instacne have better caches) but at least we are specifying the order instead of letting it random. Change-Id: Ia4e7ec7751585f337d740a1246cac379d4871995 JIRA: MESOS-4343
v1.9.109-criteo10
Filter instances that do not have a task (#34) Co-authored-by: Julien DOCHE <[email protected]> Co-authored-by: Julien Pepy <[email protected]>
v1.9.109-criteo9-rc1
Check the instance has one task before calling checkEnoughInstancesRu…
v1.9.109-criteo9
Only crash HealthCheckActor if stream for the current incarnation of …
v1.9.109-criteo8
Fix log to have also app path
v1.9.109-criteo7
Fix grace period bug (#33) Following the change of task id / instance id format, task health status was not properly tracked because bound to the same instance id after successive kills for health check failure. This fix propose to address the issue by tracking health status by task id to ensure it to cleaned each time a task is terminated, whatever the reason. Also fix similar bug with `killingInFlight` structure impacting anti-snowball.
v1.9.109-rc4
Won't do