[
https://issues.apache.org/jira/browse/ATLAS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905390#comment-14905390
]
Venkatesh Seetharam commented on ATLAS-179:
-------------------------------------------
Few questions/concerns:
* why do we need a thread pool?
* Lets use the factory method in Executors.newSingleThreadExecutor()
* Above simplifies everything and don't need to even get HiveConf
* HiveConf should be gotten from HookContext
* IMHO, the sync or async should be the prerogative of HiveHook semantics and
doing this for every hook does not make sense
> Atlas hook causes mem leak and hive server 2 crashes
> ----------------------------------------------------
>
> Key: ATLAS-179
> URL: https://issues.apache.org/jira/browse/ATLAS-179
> Project: Atlas
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Priority: Critical
>
> Two issues:
> 1. While queueing for ThreadPoolExecutor, we add hive query plan. Looks like
> query plan contains the fetch tasks and their job confs. Job confs contain
> java.util.Properties and can be huge
> 2. We have unbounded queue in ThreadPoolExecutor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
