[
https://issues.apache.org/jira/browse/FLINK-16721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068541#comment-17068541
]
Chesnay Schepler commented on FLINK-16721:
------------------------------------------
I don't see any inherent inconsistencies between the files you provided. The
cpu trend shows some small CPU usage, while the thread info shows many threads
being busy between 1-4% of the time, which when added up provide a reasonable
argument for there being some CPU usage.
What makes you think that there is anything wrong?
> getProcessCpuLoad seems to report a wrong cpu load
> ---------------------------------------------------
>
> Key: FLINK-16721
> URL: https://issues.apache.org/jira/browse/FLINK-16721
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.10.0
> Reporter: xiaogang zhou
> Priority: Major
> Attachments: busythreads.txt, cpu trend.png
>
>
> I am monitoring the flink_taskmanager_Status_JVM_CPU_Load in the prometheus.
> As there is some random spikes (see attachment in cpu trend), but when i use
> some tool to get the thread load(using the analytical tool:
> https://github.com/oldratlee/useful-scripts/blob/master/show-busy-java-threads)
> , I didn't see any abnormal(see busythreads attachment)
>
> And then I found the issue about mxBean::getProcessCpuLoad in stackoverflow.
> [https://stackoverflow.com/questions/38421242/operatingsystemmxbean-getsystemcpuload-and-getprocesscpuload-values]
> some one suggest the metric can be inaccurate in some cases.
> Can anybody help me understand what's going on in my case?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
