[
https://issues.apache.org/jira/browse/LENS-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323738#comment-15323738
]
Puneet Gupta commented on LENS-1168:
------------------------------------
+1 for approach 2. Query submitter thread can use a pool of launchers. This
will be simpler and easier to maintain .
We can add driver level constraints on how many queries can be in LAUNCHING
state at any time, for hive it can be 1 and for jdbc it can be many.
> Isolate submissions for each driver
> -----------------------------------
>
> Key: LENS-1168
> URL: https://issues.apache.org/jira/browse/LENS-1168
> Project: Apache Lens
> Issue Type: Improvement
> Components: server
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 2.6
>
>
> We need to isolate query submitters for each driver to be different. We have
> seen scenarios where hive submission takes time and other interactive queries
> on jdbc are queued because querysubmitter was busy.
> Also, each driver can have a pool of submitters - which should benefit
> interactive queries with immediate submissions, especially the ones submitted
> on EXECUTE_WITH_TIMEOUT
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
