-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
cAdvisor running in docker ignore isolcpus #2792
Comments
@shohamd4 there is something clearly wrong with handling isolcpus and tasksets. I will take a look into this. |
Environment: 4-core aarch64 system.
"cpu": {
"usage": {
"total": 567239332835,
"per_cpu_usage": [
0
],
"user": 567560000000,
"system": 80000000
}
}
|
And the culprit is: cadvisor/container/libcontainer/handler.go Line 815 in 730e7df
According to the manual:
I believe that this function and any filtering that uses it must be removed: |
@iwankgb - Thank you very much for the quick fix, I'll try it on Monday. |
Hi, looks great, do you plan to push it into an official release? |
As soon as it gets merged :) |
Hi,
I'm running cAdvisor in docker on machines with high CPU load.
I've configured the server kernel with isolcpus=1,2,3
I'm running cAdvisor with the following params:
I've noticed that cAdvisor still runs on all cpus (not only cpu 0).
If I run cAdvisor with docker --cpuset-cpus=0, then cAdvisor doesn't show info on the other cpus.
Also if I enforce cpu affinity with taskset (without the --cpuset-cpus flag) - cAdvisor will show me stats only on the allowed cpus.
What is the correct way to run cAdvisor on a specific cpu?
BTW, I can see that setting -max_procs to 1 doesn't affect the number of processes that cAdvisor uses.
Thanks,
Doron
The text was updated successfully, but these errors were encountered: