[
https://issues.apache.org/jira/browse/HIVE-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556785#comment-16556785
]
Naveen Gangam commented on HIVE-14162:
--------------------------------------
[~stakiar] I took a quick look at the patch. Just thinking out loud here. Are
spark sessions created by HoS always as a same user? or do they depend on the
hive user? In other words, when a spark job is submitted by hive, do different
hive users share the same spark session? or does it depend on
{{hs2.enable.doAs}} similar to HoMR?
If there is a new session for each hive user, then there will be many users at
the same time. This fix adds a new single-threaded thread pool to monitor the
session timeout for each session. Should we be concerned about the number of
threads we add to the JVM for such scenarios? Thanks
> Allow disabling of long running job on Hive On Spark On YARN
> ------------------------------------------------------------
>
> Key: HIVE-14162
> URL: https://issues.apache.org/jira/browse/HIVE-14162
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Thomas Scott
> Assignee: Sahil Takiar
> Priority: Major
> Attachments: HIVE-14162.1.patch, HIVE-14162.2.patch,
> HIVE-14162.3.patch
>
>
> Hive On Spark launches a long running process on the first query to handle
> all queries for that user session. In some use cases this is not desired, for
> instance when using Hue with large intervals between query executions.
> Could we have a property that would cause long running spark jobs to be
> terminated after each query execution and started again for the next one?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
