You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zoltan Haindrich (Jira)" <ji...@apache.org> on 2021/01/26 13:49:00 UTC
[jira] [Resolved] (HIVE-24411) Make ThreadPoolExecutorWithOomHook
more awareness of OutOfMemoryError
[ https://issues.apache.org/jira/browse/HIVE-24411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltan Haindrich resolved HIVE-24411.
-------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
merged into master. Thank you [~dengzh]!
> Make ThreadPoolExecutorWithOomHook more awareness of OutOfMemoryError
> ---------------------------------------------------------------------
>
> Key: HIVE-24411
> URL: https://issues.apache.org/jira/browse/HIVE-24411
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Now the ThreadPoolExecutorWithOomHook invokes some oom hooks and stops the HiveServer2 in case of OutOfMemoryError when executing the tasks. The exception is obtained by calling method _future.get()_, however the exception should not be an instance of OutOfMemoryError, as the exception is wrapped in ExecutionException, refer to the method _report_ in FutureTask.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)