*strong text*It appears that when I have multiple health checks, the deployment of a task will complete as soon as a single health check succeeds rather than waiting for all health checks to succeed. That means the old task will be killed before the new task has reached a healthy state.
Is this expected behavior? I'd rather it wait for all health checks to succeed.
I've observed this through the UI, but I can't see it in the logs, because I don't see the log statements from the HealthCheckActor.
Here is the JSON I am posting to marathon: