Support Questions

Find answers, ask questions, and share your expertise
Celebrating as our community reaches 100,000 members! Thank you!

UnknownHostException Exception while inserting into Hive table



I am getting this error when trying to insert into a hive table, the host in question (hdata2) is accessible and other services are running fine from it.

klist shows valid kerberos ticket. I want to merge many tables into one, so was inserting executing external hql script.

Any idea where to look for, logs looks fine.

INFO : Tez session hasn't been created yet. Opening session ERROR : Failed to execute tez graph. java.lang.IllegalArgumentException: hdata2.xxxxxxxxxxxx.local at at org.apache.hadoop.yarn.util.timeline.TimelineUtils.buildTimelineTokenService( at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit( at org.apache.hadoop.service.AbstractService.init( at org.apache.tez.client.TezYarnClient.init( at org.apache.tez.client.TezClient.start( at at org.apache.hadoop.hive.ql.exec.tez.TezTask.updateSession( at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute( at org.apache.hadoop.hive.ql.exec.Task.executeTask( at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential( at org.apache.hadoop.hive.ql.Driver.launchTask( at org.apache.hadoop.hive.ql.Driver.execute( at org.apache.hadoop.hive.ql.Driver.runInternal( at at at org.apache.hive.service.cli.operation.SQLOperation.runQuery( at org.apache.hive.service.cli.operation.SQLOperation.access$300( at org.apache.hive.service.cli.operation.SQLOperation$2$ at Method) at at at org.apache.hive.service.cli.operation.SQLOperation$ at java.util.concurrent.Executors$ at at java.util.concurrent.Executors$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: hdata2.xxxxxxxxxxxx.local ... 30 more Error: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask (state=08S01,code=1)




Expert Contributor

This is due to nodes in cluster cannot resolve names correctly.

Could be a node manager node or the very edge node (if running from there) where Beeline is started.

Need to ensure that, if using DNS, resolution occurs at low latency, if using /etc/hosts, this file needs to be checked across cluster nodes