使用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?

主题
容器AWS 上的 .NET
标签
亚马逊弹性容器服务 (ECS)AWS 上的 .NET
语言
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

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈，并能促进提问者的职业发展。

回答问题的准则

相关内容