Can the memory checked inside the ecs fargate and the memory of the task definition be different?

0

I set 1 vcpu/ 2 memory in task definition in aws ecs fargate.

To check the memory of the app inside, I accessed the container directly through the aws exceute command and checked the memory through free and top, but it was set to 8gb. Why did this happen?

joker
demandé il y a un an447 vues
1 réponse
1
Réponse acceptée

, it's possible that you're seeing the total memory available to the underlying infrastructure (the EC2 instance) rather than the memory limit set for your specific Fargate task. Fargate abstracts the underlying server infrastructure, but when you run commands like free or top inside a container, they report information about the underlying host, not the individual container.

The memory value that you set in the task definition is used by AWS to allocate resources and to enforce memory limits, but it might not be directly visible inside the container using tools like free or top.

To investigate further, you might consider monitoring the memory usage of your task using CloudWatch, or looking into container-level monitoring tools which are designed to report metrics in a containerized environment.

profile picture
EXPERT
répondu il y a un an
profile picture
EXPERT
vérifié il y a 11 jours
profile picture
EXPERT
vérifié il y a un mois
  • I said " it's possible that you're seeing the total memory available to the underlying infrastructure (the EC2 instance) ", but I don't understand the "infrastructure (the EC2 instance)" part, so I have an additional question. Can you say that infrastructure (the EC2 instance) is the server that actually operated fargate? fargate is confusing me as it doesn't use ec2 services.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions