[ 
https://issues.apache.org/jira/browse/HIVE-21555?focusedWorklogId=442921&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-442921
 ]

ASF GitHub Bot logged work on HIVE-21555:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Jun/20 16:12
            Start Date: 09/Jun/20 16:12
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #585:
URL: https://github.com/apache/hive/pull/585#issuecomment-641143716


   This pull request has been automatically marked as stale because it has not 
had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the [email protected] list if the patch is in 
need of reviews.


----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 442921)
    Time Spent: 20m  (was: 10m)

> [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
>         Attachments: 1.patch
>
>          Time Spent: 20m
>  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.
> PR: https://github.com/apache/hive/pull/585



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to