Crashing ECS Scheduled Task Remains Running


We have a Java Spring Boot ECS Fargate Scheduled Task that has been running every hour for many months with no issues. On April 8, we noticed that our containers stopped terminating themselves on failure, and we racked up a decent bill once we noticed that we had hundreds of "running" containers that were simply doing nothing. I've looked at the logs and while we did see a spate of failures recently, we've seen similar/identical errors previously but with containers that terminated themselves. These tasks are connecting to Redis and getting an OOM error (which still needs looked into as well), but I think that problem simply surfaced this other much more costly problem. Has there been a change in behavior for scheduled tasks?

1 réponse
Réponse acceptée

If the process started by the ENTRYPOINT does not terminate instance will remain running. That is the only way I know to have a container instance self-terminate.

profile picture
répondu il y a un an
  • Turns out, we had added a service that was holding a thread open and preventing the rest of the container from terminating.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions