Description:
In the topic we found out that OOM killer killing repeatedly vmagent. Is there some option to limit used memory by vmagent?
Version:
pmm-client: Version: 2.41.1
In the topic we found out that OOM killer killing repeatedly vmagent. Is there some option to limit used memory by vmagent?
pmm-client: Version: 2.41.1
@Jakub_Noga
You can check [PMM-9374] - Percona JIRA for examples.
TLDR: start the PMM server with -e VMAGENT_memory_allowedBytes flag, and all your agents should have it.
There are known bug, that not all parameters are working properly, you can see the list in
https://perconadev.atlassian.net/browse/PMM-11826
Thank you for your reply. Unfortunately setting ENV on the server side didn’t affect the client.
The container has a limit of 5GB and vmagent is still working over the defined VMAGENT_memory_allowedBytes
that is 3GB
at the moment. Info from dmesg:
Killed process 296139 (vmagent) total-vm:5999408kB, anon-rss:4397708kB, file-rss:8844kB, shmem-rss:0kB, UID:1002 pgtables:9372kB oom_score_adj:0
Is the option already implemented in our version (now 2.41.2
)
@Roma_Novikov Any update?
Unanswered | Unsolved | Solved
MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright © 2006 - 2024 Percona LLC. All rights reserved.