[
https://issues.apache.org/jira/browse/HIVE-21555?focusedWorklogId=221060&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-221060
]
ASF GitHub Bot logged work on HIVE-21555:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Apr/19 02:19
Start Date: 01/Apr/19 02:19
Worklog Time Spent: 10m
Work Description: bd2019us commented on pull request #585: [HIVE-21555]
fix a high risk in memory error
URL: https://github.com/apache/hive/pull/585
Fix: [#HIVE-21555](https://issues.apache.org/jira/browse/HIVE-21555).
The cached thread pool is proper when the task is light-weight and the
number of sub-threads are not too many. Otherwise, fixed thread pool should be
used to avoid OutOfMemoryError.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 221060)
Time Spent: 10m
Remaining Estimate: 0h
> [SECURITY]newCachedThreadPool() has higher risk in causing OutOfMemoryError
> ---------------------------------------------------------------------------
>
> Key: HIVE-21555
> URL: https://issues.apache.org/jira/browse/HIVE-21555
> Project: Hive
> Issue Type: Bug
> Reporter: bd2019us
> Assignee: bd2019us
> Priority: Major
> Labels: patch
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Location:
> ql/src/java/org/apache/hadoop/hive/ql/processors/LlapCacheResourceProcessor.java:136
> In the program, since the number of instances (instances =
> llapRegistryService.getInstances().getAll();) is not known ahead of time, it
> has a high risk in causing OutOfMemoryError when too many threads are
> created. Therefore, to ensure security, a fixed number of thread pool should
> be used, which can be freely configured and also enables running multiple
> instances concurrently but is free from the above error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
