Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
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?

Argomenti
Container.NET su AWS
Tag
Servizio container Amazon Elastic.NET su AWS
Lingua
English
AWS-User-0742604
posta 2 anni fa589 visualizzazioni
1 Risposta
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
con risposta 2 anni fa
  • AWS-User-0742604
    2 anni fa

    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 anni fa

    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 anni fa

    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

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente