[
https://issues.apache.org/jira/browse/HIVE-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876805#comment-14876805
]
WangMeng commented on HIVE-11149:
---------------------------------
[~sershe] According to my understanding,it may not occur the problem you
mentioned above.
According to code logic in Hive,each thread accessing the session owns the
initial default value"resetPerfLogger == true" when it begin initialization and
then it registered as ThreadLocal thread by perfLogger.set() method.
Do I understand your problem? Thanks.
//Reset the perf logger in Driver.runInternal()
PerfLogger perfLogger = PerfLogger.getPerfLogger(true);
//PerfLogger.java
public static PerfLogger getPerfLogger(boolean resetPerfLogger) {
if (SessionState.get() == null) {
if (perfLogger.get() == null || resetPerfLogger) {
perfLogger.set(new PerfLogger());
}
return perfLogger.get();
} else {
perfLogger.set(SessionState.get().getPerfLogger(resetPerfLogger));
return perfLogger.get();
}
}
> Fix issue with sometimes HashMap in PerfLogger.java hangs
> ----------------------------------------------------------
>
> 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, HIVE-11149.02.patch,
> HIVE-11149.03.patch
>
>
> In Multi-thread environment, sometimes the 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)
