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

Alexander Pivovarov commented on HIVE-10569:
--------------------------------------------

I tried this with hive-0.13.1. The query works fine for me
{code}
hive> set hive.exec.parallel=true;
hive> set hive.execution.engine=tez;
hive> create table sometable(somecol INT);
OK
Time taken: 3.363 seconds

hive> select count(*) from sometable;
Query ID = myapp_20150514182020_ac958b79-4939-4092-a1b7-4bf58036dca5
Total jobs = 1
Launching Job 1 out of 1


Status: Running (application id: application_1431616132488_3229)

Map 1: -/-      Reducer 2: 0/1  
Map 1: -/-      Reducer 2: 0/1  
Map 1: -/-      Reducer 2: 0/1  
Map 1: -/-      Reducer 2: 1/1  
Status: Finished successfully
OK
0
Time taken: 14.551 seconds, Fetched: 1 row(s)
{code}

> 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.1.0
>            Reporter: Rohit Agarwal
>            Priority: Critical
>         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)

Reply via email to