You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/07/03 09:59:00 UTC
[jira] [Closed] (FLINK-16721) getProcessCpuLoad seems to report a
wrong cpu load
[ https://issues.apache.org/jira/browse/FLINK-16721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-16721.
------------------------------------
Resolution: Cannot Reproduce
> 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)