Health Check Grace Period Ecs. If so, that seems like a severe limitation. Max number of failed health checks to mark containers as unhealthy and terminate.
We have now enabled the ability to configure a grace period for every node auto scaled by ocean. We have been trying to add a health check on the task definition, however it refuses to work. Previously, if amazon ecs tasks took a long time to start, elastic load balancing (elb) health checks could mark the task as unhealthy and the service scheduler would shut the task down prematurely.
I am trying to use the cloudformation codedeploy blue/green deployment feature so have a task set that looks like the following.
(i tried this but the problem still occurred, ecs just waited longer to restart the task after the spurious health check failures.) Count in seconds for which service will ignore health after launching targets. (true story!) in that case, increase the default grace period from 0s to e.g. I am trying to use the cloudformation codedeploy blue/green deployment feature so have a task set that looks like the following.