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
已提問 1 年前檢視次數 438 次
1 個回答
0
已接受的答案

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
已回答 1 年前
  • Turns out, we had added a service that was holding a thread open and preventing the rest of the container from terminating.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南