-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Feature Request: cgroupv2 support #130
Comments
We can refer to uber-go/automaxprocs@ad6f05b and uber-go/automaxprocs@721b013 . I will take a look at this when I have time. |
According to this PR, cgroups v2 support was added. @PureWhiteWu can you give an example of the issue? For context, I'm debugging some odd behaviour with bad logical CPUs detection under Kubernetes, and I'm interested to see if there's still a bug in some case (when memory limit isn't specified in the |
@asfaltboy Yes, the cgroups v2 seems not working correctly on our kubernetes environment. |
@PureWhiteWu did you end up investigating this more? |
Sorry for the late reply, too busy these days. I haven't find a standard way to get the cpu nums from k8s environment with different resource visibility plans (lxcfs or not). I'll spend some time investigate this asap. |
Currently num_cpus doesn't support cgroupv2, maybe we should support it?
Spec: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
K8s ref: https://kubernetes.io/docs/concepts/architecture/cgroups/
The text was updated successfully, but these errors were encountered: