[ https://issues.apache.org/jira/browse/HIVE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523614#comment-14523614 ]
Rohit Agarwal commented on HIVE-10569: -------------------------------------- To reproduce this hang, you can follow these steps: 1. Run hadoop in distributed or pseudodistributed mode. (We were running hadoop-2.6.0 on our clusters when I first saw this. I was able to reproduce this in the pseudodistributed mode but not in the local mode.) 2. Install hive. (I was able to reproduce it on 0.13.1 and 1.1.0) 3. Install tez jars in the hadoop classpath (but don't setup tez.lib.uris - because we want SessionState.start to throw an exception.) 4. Run hive {code} set hive.exec.parallel=true; set hive.execution.engine=tez; create table sometable(somecol INT); select count(*) from sometable; --this query will hang after printing an exception. With the attached patch, we will get the prompt back. {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)