Health checks seem to be broken. This was discovered in the SI test `test_health_failed_check`
It launches an app with the following:
It detects the port defined as PORT0 then blocks the inbound of that port on the node that the task is running on for 7 seconds (longer than 2 seconds)
normally the unhealthy is determined and the task is killed and relaunched. There is no unhealthy detection in the latest marathon.
it appears there are recent changes in this area of code:
it looks like custom timeouts may not be implemented in the latest changes...
here is readiness checks: https://github.com/mesosphere/marathon/blob/83a5e99a72b42fffd28e649869ec0617652b2d84/src/main/scala/mesosphere/marathon/core/readiness/impl/ReadinessCheckExecutorImpl.scala#L82
timeouts for health checks are not set: