[
https://issues.apache.org/jira/browse/HIVE-11969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938961#comment-14938961
]
Sergey Shelukhin edited comment on HIVE-11969 at 9/30/15 10:15 PM:
-------------------------------------------------------------------
Container prewarm remains part of the init so it's not affected.
The CLI startup should be decoupled from Tez session startup because not all
queries use Tez; user can do number of operations like
set/describe/create/explain/..., or even just take time typing a query, before
the session is even needed. There are also stats queries and local fetches that
don't require the session.
If the query hangs, it will be visible that the query has not started. IMHO it
is actually better because you can then check the state of the cluster to see
what's going on.
was (Author: sershe):
Container prewarm remains part of the init so it's not affected.
The CLI startup should be decoupled from Tez session startup because not all
queries use Tez; user can do number of operations like
set/describe/create/explain/..., or even just typing a query, before the
session is even needed. There are also stats queries and local fetches that
don't require the session.
If the query hangs, it will be visible that the query has not started. IMHO it
is actually better because you can then check the state of the cluster to see
what's going on.
> start Tez session in background when starting CLI
> -------------------------------------------------
>
> Key: HIVE-11969
> URL: https://issues.apache.org/jira/browse/HIVE-11969
> Project: Hive
> Issue Type: Bug
> Components: Tez
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-11969.01.patch, HIVE-11969.patch
>
>
> Tez session spins up AM, which can cause delays, esp. if the cluster is very
> busy.
> This can be done in background, so the AM might get started while the user is
> running local commands and doing other things.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
