You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Prasanth Jayachandran (Jira)" <ji...@apache.org> on 2020/06/02 00:30:00 UTC
[jira] [Updated] (HIVE-21624) LLAP: Cpu metrics at thread level is
broken
[ https://issues.apache.org/jira/browse/HIVE-21624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasanth Jayachandran updated HIVE-21624:
-----------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to master. Thanks Ashutosh for the review!
> LLAP: Cpu metrics at thread level is broken
> -------------------------------------------
>
> Key: HIVE-21624
> URL: https://issues.apache.org/jira/browse/HIVE-21624
> Project: Hive
> Issue Type: Bug
> Components: llap
> Affects Versions: 4.0.0, 3.2.0
> Reporter: Nita Dembla
> Assignee: Prasanth Jayachandran
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21624.1.patch, HIVE-21624.2.patch, HIVE-21624.3.patch, HIVE-21624.4.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ExecutorThreadCPUTime and ExecutorThreadUserTime relies on thread mx bean cpu metrics when available. At some point, the thread name which the metrics publisher looks for has changed causing no metrics to be published for these counters.
> The above counters looks for thread with name starting with "ContainerExecutor" but the llap task executor thread got changed to "Task-Executor"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)