hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10569) Hive CLI gets stuck when hive.exec.parallel=true; and some exception happens during SessionState.start
Date Wed, 20 May 2015 04:51:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551806#comment-14551806
] 

Ashutosh Chauhan commented on HIVE-10569:
-----------------------------------------

[~ragarwal] If you are enabling exec.parallel in your environment you might also get hit by
HIVE-10404 so you may want to tackle that one too.

> Hive CLI gets stuck when hive.exec.parallel=true; and some exception happens during SessionState.start
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-10569
>                 URL: https://issues.apache.org/jira/browse/HIVE-10569
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.13.1, 1.2.0, 1.1.0
>            Reporter: Rohit Agarwal
>            Assignee: Rohit Agarwal
>            Priority: Critical
>             Fix For: 1.3.0
>
>         Attachments: HIVE-10569.patch
>
>
> The CLI gets stuck in the loop in [DriverContext.pollFinished | https://github.com/apache/hive/blob/release-1.1.0/ql/src/java/org/apache/hadoop/hive/ql/DriverContext.java#L108]
when some {{TaskRunner}} which has completed has not been marked as non-running.
> This can happen when there is exception in [SessionState.start | https://github.com/apache/hive/blob/release-1.1.0/ql/src/java/org/apache/hadoop/hive/ql/exec/TaskRunner.java#L74]
which is called from {{TaskRunner.run}}.
> This happened with us when we were running with {{hive.exec.parallel=true}}, {{hive.execution.engine=tez}}
and Tez wasn't correctly setup.
> In this case the CLI printed the exception and then got hung (No prompt.)
> A simple fix is to call {{result.setRunning(false);}} in the {{finally}} block of {{TaskRunner.run}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message