Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

When running a query in Hive against an HBase table, the Hadoop job goes into kill status

When running a query in Hive against an HBase table, the Hadoop job goes into kill status

Explorer
  • When I run a Hive query on the HBase table, the job gets to 40% and then gets killed. 
  • Can you tell me why the Hive query is being killed?

4 REPLIES 4

Re: When running a query in Hive against an HBase table, the Hadoop job goes into kill status

Master Guru
How many files does your query generate before this happens?

Hive may kill jobs if they produce too many files, as one reason. This can
be controlled via something like "SET hive.exec.max.created.files=655350;"

Do you see any error of the below form at the client or in the task logs?
That may help confirm if its cause of this.

ERROR org.apache.hadoop.hive.ql.exec.Task: [Fatal Error] total number
of created files now is 100008, which exceeds 100000. Killing the job.


Re: When running a query in Hive against an HBase table, the Hadoop job goes into kill status

Explorer

Thanks Harsh for your precisous time ,

 

At the tail end of the Hive log that shows the query gets to the map-reduce stage before it gets killed

Re: When running a query in Hive against an HBase table, the Hadoop job goes into kill status

Explorer

Hi Harsh,

 

I am able to see the error in the below form

 

org.apache.hadoop.hive.ql.exec.persistence.RowContainer: RowContainer created

Re: When running a query in Hive against an HBase table, the Hadoop job goes into kill status

Explorer

Hi Anyone can help me on this