[
https://issues.apache.org/jira/browse/HIVE-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574832#comment-14574832
]
Sergey Shelukhin commented on HIVE-10944:
-----------------------------------------
synchronized (as far as I can see) call to isInitialized from
incrementMetricsCounter might affect perf for parallel workloads, like we saw
before with locks in logging, kryo, and HDFS code. Also config checks in other
places may not be cheap. Is it possible to cache those values, I assume once
initialized it won't change back to false?
> Fix HS2 for Metrics
> -------------------
>
> Key: HIVE-10944
> URL: https://issues.apache.org/jira/browse/HIVE-10944
> Project: Hive
> Issue Type: Bug
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: HIVE-10944.patch
>
>
> Some issues about initializing the new HS2 metrics
> 1. Metrics is not working properly in HS2 due to wrong init checks
> 2. If not enabled, JVMPauseMonitor logs trash to HS2 logs as it wasnt
> checking if metrics was enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
