[ https://issues.apache.org/jira/browse/HIVE-24411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihua Deng updated HIVE-24411: ------------------------------- Description: 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. (was: 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 may never be an instance of OutOfMemoryError, as the exception is wrapped in ExecutionException, refer to the method _report_ in FutureTask.) > 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 > Time Spent: 40m > 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)