question Re: Hive CLI unresponsive in Archives of Support Questions (Read Only)

Hive CLI unresponsive

bsaini — Fri, 09 Oct 2015 22:38:29 GMT

A prospect is experiencing issue with Hive CLI. I know Hive CLI is not a long term solution and beeline is preferred but I am wondering if beeline, Hive View and other front end tools are working, what could cause Hive CLI to not start -

$ hive
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/hdp/2.3.0.0-2557/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/hdp/2.3.0.0-2557/spark/lib/spark-assembly-1.3.1.2.3.0.0-2557-hadoop2.7.1.2.3.0.0-2557.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
WARNING: Use "yarn jar" to launch YARN applications.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/hdp/2.3.0.0-2557/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/hdp/2.3.0.0-2557/spark/lib/spark-assembly-1.3.1.2.3.0.0-2557-hadoop2.7.1.2.3.0.0-2557.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Logging initialized using configuration in file:/etc/hive/2.3.0.0-2557/0/hive-log4j.properties

Re: Hive CLI unresponsive

dtraver — Fri, 09 Oct 2015 22:40:46 GMT

Can you try setting the HiveCLI to startup with DEBUG logging?

e.g.

hive -hiveconf hive.log.file=hivecli_debug.log -hiveconf hive.log.dir=/tmp/hivecli -hiveconf hive.root.logger=DEBUG,DRFA

-Darwin

Re: Hive CLI unresponsive

deepesh1 — Fri, 09 Oct 2015 22:43:29 GMT

One thing to check is if they are using tez. If they are, it could be possible that they do not have any capacity on their YARN cluster to launch AM. So the Hive CLI waits indefinitely to launch an AM. One thing they can do to alleviate this is to launch hive cli as "hive -hiveconf hive.execution.engine=mr".

Re: Hive CLI unresponsive

bsaini — Fri, 09 Oct 2015 23:33:31 GMT

Hey Deepesh, thanks for the answer.. I am wondering why would MR get resources and not Tez?

Re: Hive CLI unresponsive

deepesh1 — Fri, 09 Oct 2015 23:46:15 GMT

Its not that MR gets resources, Tez just pre-allocates resources, it starts a YARN application as soon as you invoke the Hive CLI. In case of MR a YARN application is launched only when its required by the executing query. This is a performance optimization in Hive on Tez saving the user the overhead of launching a AM everytime a new query is run in the same Hive CLI session.

Re: Hive CLI unresponsive

pbalasundaram — Sat, 10 Oct 2015 03:39:59 GMT

Hint: If you are on HDP 2.2, I have seen similar issue .

The issue arises immediately after a configuration change is set using ambari. Beeline would then connect fine, but the Hive CLI will hang. This would then appear to the customer as being introduced by ambari .

Rolling back the change in ambari fixes the issue, but then setting a new configuration is blocked.

Re: Hive CLI unresponsive

deepesh1 — Sat, 10 Oct 2015 04:09:22 GMT

Can you shed more details on what type of configuration change was applied using Ambari that triggered the hive cli hang?

Re: Hive CLI unresponsive

nsabharwal — Sat, 10 Oct 2015 19:15:40 GMT

@bsaini@hortonworks.com

I would start with queues. Have your configures Yarn Queues to have multiple job? Please check if there are any other jobs. By default, if there is one long job running then Hive CLI wont respond back until the running job finishes.

Re: Hive CLI unresponsive

pratapkumar_nan — Tue, 08 Mar 2016 01:36:37 GMT

I am new to hadoop . I have the same issue .Can anyone help me .

Re: Hive CLI unresponsive

demarkle — Wed, 22 Jun 2016 03:07:16 GMT

In our case this was caused by the queues being stopped in yarn due to an upgrade. We changed the queues from STOPPED to RUNNING in capacity-scheduler.xml then restarted yarn and the problem was fixed.

Re: Hive CLI unresponsive

joshua_adeleke — Fri, 21 Oct 2016 12:07:04 GMT

@Deepesh If i still want to use Tez as my hive execution engine, what do i need to do? I am running a sqoop job (with Oozie) to move data from oracle into hive. As advised above, i changed to MR and it worked but our hive execution engine of choice is Tez. My Tez container size is 1GB. What changes need to be made for Tez to be able to launch AM for the sqoop process? @Benjamin Leonhardi

Re: Hive CLI unresponsive

joshua_adeleke — Fri, 21 Oct 2016 19:25:45 GMT

This was resolved by reducing the reduced amount of memory to be used by the AM to 2048 from 4096 (changing the tez config parameter tez.am.resource.memory.mb)

Re: Hive CLI unresponsive

zack_riesland — Tue, 27 Jun 2017 23:23:52 GMT

This was helpful for me