hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Nastetsky (JIRA)" <>
Subject [jira] [Commented] (HIVE-7186) Unable to perform join on table
Date Fri, 20 Jun 2014 14:17:24 GMT


Alex Nastetsky commented on HIVE-7186:

I just saw a similar problem with with a different stacktrace. This time, the join got to
the very end of the job and failed as it finished:
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Premature EOF:
no length prefix available
	at org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler.handleEvent(
	at org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler.serviceStop(
	at org.apache.hadoop.service.AbstractService.stop(
	at org.apache.hadoop.service.ServiceOperations.stop(
	at org.apache.hadoop.service.ServiceOperations.stopQuietly(
	at org.apache.hadoop.service.CompositeService.stop(
	at org.apache.hadoop.service.CompositeService.serviceStop(
	at org.apache.hadoop.service.AbstractService.stop(
Caused by: Premature EOF: no length prefix available
	at org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(
	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.transfer(
	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.addDatanode2ExistingPipeline(
	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.setupPipelineForAppendOrRecovery(
	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(
	at org.apache.hadoop.hdfs.DFSOutputStream$

> Unable to perform join on table
> -------------------------------
>                 Key: HIVE-7186
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>         Environment: Hortonworks Data Platform
>            Reporter: Alex Nastetsky
> Occasionally, a table will start exhibiting behavior that will prevent it from being
used in a JOIN. 
> When doing a map join, it will just stall at "Starting to launch local task to process
map join; ".
> When doing a regular join, it will make progress but then error out with a IndexOutOfBoundsException:
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: java.lang.IndexOutOfBoundsException
>         at org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.processOp(
>         at org.apache.hadoop.hive.ql.exec.Operator.process(
>         at org.apache.hadoop.hive.ql.exec.Operator.forward(
>         at org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(
>         at org.apache.hadoop.hive.ql.exec.Operator.process(
>         at org.apache.hadoop.hive.ql.exec.Operator.forward(
>         at org.apache.hadoop.hive.ql.exec.MapOperator.process(
>         ... 9 more
> Caused by: java.lang.IndexOutOfBoundsException
>         at java.nio.Buffer.checkIndex(
>         at java.nio.ByteBufferAsIntBufferL.put(
>         at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.collect(
>         at org.apache.hadoop.mapred.MapTask$OldOutputCollector.collect(
>         at org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.collect(
>         at org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.processOp(
>         ... 15 more
> Doing simple selects against this table work fine and do not show any apparent problems
with the data.
> Assume that the table in question is called tableA and was created by queryA.
> Doing either of the following has helped resolve the issue in the past.
> 1) create table tableB as select * from tableA;
>   Then just use tableB instead in the JOIN.
> 2) regenerate tableA using queryA
>   Then use tableA in the JOIN again. It usually works the second time.
> When doing a "describe formatted" on the tables, the totalSize will be different between
the original tableA and tableB, and sometimes (but not always) between the original tableA
and the regenerated tableA. The numRows will be the same across all versions of the tables.
> This problem can not be reproduced consistently, but the issue always happens when we
try to use an affected table in a JOIN.

This message was sent by Atlassian JIRA

View raw message