You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "slim bouguerra (JIRA)" <ji...@apache.org> on 2018/03/14 19:09:00 UTC
[jira] [Work stopped] (HIVE-18959) Avoid creating extra pool of
threads within LLAP
[ https://issues.apache.org/jira/browse/HIVE-18959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HIVE-18959 stopped by slim bouguerra.
---------------------------------------------
> Avoid creating extra pool of threads within LLAP
> ------------------------------------------------
>
> Key: HIVE-18959
> URL: https://issues.apache.org/jira/browse/HIVE-18959
> Project: Hive
> Issue Type: Task
> Components: Druid integration
> Environment: Kerberos Cluster
> Reporter: slim bouguerra
> Assignee: slim bouguerra
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18959.patch
>
>
> The current Druid-Kerberos-Http client is using an external single threaded pool to handle retry auth calls (eg when a cookie expire or other transient auth issues).
> First, this is not buying us anything since all the Druid Task is executed as one synchronous task.
> Second, this can cause a major issue if an exception occurs that leads to shutting down the LLAP main thread with an exception like:
> {code} org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Thread Thread[KerberosHttpClient... threw an Exception. Shutting down now...{code}
> Thus to fix this we should avoid using an external thread pool and handle retrying in a synchronous way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)