ECS Fargate container running ASP.NET image not garbage collecting

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

태그

아마존 엘라스틱 컨테이너 서비스 AWS의 .NET

언어

English

AWS-User-0742604

질문됨 2년 전589회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

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.

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

ECS Fargate container running ASP.NET image not garbage collecting

관련 콘텐츠