[
https://issues.apache.org/jira/browse/HIVE-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608830#comment-14608830
]
Sergey Shelukhin commented on HIVE-11149:
-----------------------------------------
-1 for now
isn't that supposed to be handled by threadlocal perflogger? Places that don't
use it should use it instead; perhaps ctors should be hidden.
All the threads will add/remove methods with the same names as far as I see,
which with concurrenthashmap will result in different errors (perflogger-level)
or at least incorrect logging.
> Fix issue with Thread unsafe Class HashMap in PerfLogger.java hangs in
> Multi-thread environment
> ---------------------------------------------------------------------------------------------------
>
> Key: HIVE-11149
> URL: https://issues.apache.org/jira/browse/HIVE-11149
> Project: Hive
> Issue Type: Bug
> Components: Logging
> Affects Versions: 1.2.0
> Reporter: WangMeng
> Assignee: WangMeng
> Attachments: HIVE-11149.01.patch
>
>
> In Multi-thread environment, the Thread unsafe Class HashMap in
> PerfLogger.java will casue massive Java Processes hang and cost large
> amounts of unnecessary CPU and Memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)