使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款
AWS re:Postre:Post

ECS Fargate container running ASP.NET image not garbage collecting

0

I have an ECS Fargate task running an ASP.NET image and I have noticed that it keeps failing due to OOM exception. I can look in CloudWatch and the memory keeps increasing. When I run in a local docker container, I can see that the garbage collector is running correctly and there is no memory problem. I have seen people suggest to set Server GC to false, but I'm not sure if that is the problem. From what I have read this should have been fixed in previous versions (I am using asp.net 5). Is this expected and is the correct approach to set this to false?

主題
容器.NET on AWS
標籤
Amazon Elastic Container Service.NET on AWS
語言
English
AWS-User-0742604
已提問 2 年前檢視次數 589 次
1 個回答
0

I will suggest to consider fine tuning web.config https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/web-config?view=aspnetcore-5.0

You may want considering hands-on help by partners to dig into issue.

AWS
k8sy
已回答 2 年前
  • AWS-User-0742604
    2 年前

    That is where I have seen the ability to turn off server garbage collection. Do you know if this is a known issue?

  • k8sy
    2 年前

    no, there is no known issue. However, if there are dangling references, GC has no way to cleanup. I'll suggest to look into code. Profiling may help

  • AWS-User-0742604
    2 年前

    I mentioned that this is not been in a local docker container. GC works just fine, which is what is leading me to think it's an ECS issue or at least difference

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

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

回答問題指南

相關內容