On Tue, 13 Apr 2021 02:00:24 GMT, Yasumasa Suenaga <ysuen...@openjdk.org> wrote:
> I got -1.0 from both CpuLoad and SystemCpuLoad in OperatingSystem MXBean when > I run the application on Fedora 33 x64 which is installed cgroups V2. > >  > > I do not run the application in the container, nor do not run with resource > limitation on cgroups, so JMX should report CPU load on host value in this > case. Hi Yasumasa, This strikes me as the wrong fix to the problem. isCpuSetSameAsHostCpuSet is only intended to be used as a simple optimization when the configured cpuset happens to match the hosts. What you are looking for is a fix to the problem when there is no cpuset set at all. It strikes me that in getCpuLoad() if there are no quotas and no effective-cpu-set and no cpusets.cpus value, then it should fallback to using the host values rather than returning -1. That said, the problem may also be that we have a containerMetrics object when no container is actually active! Perhaps that is the true bug here? Thanks, David David ------------- PR: https://git.openjdk.java.net/jdk/pull/3447
