-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix used memory calculations in docker/memory #27473
Fix used memory calculations in docker/memory #27473
Conversation
Pinging @elastic/integrations (Team:Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
"max": 7860224, | ||
"pct": 0.000672283359618831, | ||
"total": 1409024 | ||
"max": 0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this 0 look right to you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a case where V1 and V2 might be different. Max
Just indicates the cgroup's upper threshold, with 0
meaning there is no upper limit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Do you want to backport this to 7.15? 🙂 |
@jsoriano Added the correct (I think) backport tags. |
(cherry picked from commit 3365e67)
(cherry picked from commit 3365e67)
What does this PR do?
This brings the memory usage reporting for
docker/memory
in line withdocker stat
, as well ascadvisor
andcontainerd
by calculating used memory asused - inactive_file
. I'm marking this a bug, since we were the only ones using this more simplistic usage calculation.Why is it important?
This brings us in line with how container memory usage is calculated elsewhere.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
usage
indocker/memory
is a reasonable value.Related issues