Score:0

ECS: downtime due to unhealthy containers killed before replacement

mn flag

I have an ECS cluster configured with ELB healthchecks and autoscaling policy on average CPU. When there is a spike in traffic, some containers stop responding to ELB healthchecks and are marked as unhealthy. The problem is that ECS starts draining connections and killunhealthy containers before starting new ones, so it happens that I can have zero containers running before new ones are started. The autoscaling policy is not quick enough in these situations to start new containers. Ideally I would like ECS to start a new task as soon as it marks a task as unhealthy. Any idea how to solve this issue?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.