Crashing ECS Scheduled Task Remains Running

2

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?

ctucker
asked a year ago312 views
1 Answer
0
Accepted Answer

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
answered a year ago
  • Turns out, we had added a service that was holding a thread open and preventing the rest of the container from terminating.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions