question Re: Hive interactive server cant start null in Support Questions

Hive interactive server cant start null

myzard — Fri, 16 Dec 2022 07:25:03 GMT

i try to start hive llap but when i start always failed and this logs from task log

WARN conf.HiveConf: HiveConf of name hive.heapsize does not exist
ERROR cli.LlapStatusServiceDriver: FAILED: null
java.lang.NullPointerException: null
	at org.apache.hadoop.hive.llap.cli.LlapStatusServiceDriver.run(LlapStatusServiceDriver.java:199) [hive-llap-server-3.1.0.jar:3.1.0]
	at org.apache.hadoop.hive.llap.cli.LlapStatusServiceDriver.main(LlapStatusServiceDriver.java:712) [hive-llap-server-3.1.0.jar:3.1.0]
FAILED: null

Command failed after 1 tries

anybody can help ? thanks

Re: Hive interactive server cant start null

Kartik_Agarwal — Sun, 18 Dec 2022 04:07:29 GMT

Try The below solutions.

@myzard Can you compare the values of hive.heapsize on this cluster that seem to be the issue? Please adjust them depending on the memory the HiveServer2 Heap Size automatically shows you the memory available to the cluster so i.e on my 24 GB single node I dedicated 8 GB for hive.heapsize and it fires up!

Possible SLotion: 
1. Increase the llap queue resource percentage
2. Try restarting YARN service and then restarted HS2I

Re: Hive interactive server cant start null

myzard — Mon, 19 Dec 2022 02:39:57 GMT

appear new error after doing that

WARN cli.LlapStatusServiceDriver: Watch timeout 400s exhausted before desired state RUNNING is attained.
2022-12-19 09:24:02,846 - LLAP app 'llap0' current state is LAUNCHING.
2022-12-19 09:24:02,847 - LLAP app 'llap0' current state is LAUNCHING.
2022-12-19 09:24:02,847 - LLAP app 'llap0' deployment unsuccessful.

Command failed after 1 tries

Re: Hive interactive server cant start null

Kartik_Agarwal — Mon, 19 Dec 2022 03:15:06 GMT

@myzard Increase the timeout below.

You can also check after changing the below property from Ambari UI > Advance Hive-interactive-env:
Number of retries while checking LLAP app status = 40
(It will show a warning, please ignore that and save)

This should increase the timeout from 400 to 800s.

If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.