What is Hive Return Code 2 from org apache hadoop hive ql exec MapRedTask

Question

I am getting   FAILED  Execution Error  return code 2 from org apache hadoop hive ql exec MapRedTask   While trying to make a copy of a partitioned table using the commands in the hive console   CREATE TABLE copy table name LIKE table name  INSERT OVERWRITE TABLE copy table name PARTITION day  SELECT   FROM table name    I initially got some semantic analysis errors and had to set   set hive exec dynamic partition true set hive exec dynamic partition mode nonstrict   Although I m not sure what the above properties do    Full ouput from hive console   Total MapReduce jobs   1 Launching Job 1 out of 1 Number of reduce tasks determined at compile time  1 In order to change the average load for a reducer  in bytes     set hive exec reducers bytes per reducer  lt number gt  In order to limit the maximum number of reducers    set hive exec reducers max  lt number gt  In order to set a constant number of reducers    set mapred reduce tasks  lt number gt  Starting Job   job 201206191101 4557  Tracking URL   http   jobtracker 50030 jobdetails jsp jobid job 201206191101 4557 Kill Command    usr lib hadoop bin hadoop job  -Dmapred job tracker master 8021 -kill job 201206191101 4557 2012-06-25 09 53 05 826 Stage-1 map   0    reduce   0  2012-06-25 09 53 53 044 Stage-1 map   100    reduce   100  Ended Job   job 201206191101 4557 with errors FAILED  Execution Error  return code 2 from org apache hadoop hive ql exec MapRedTask

User · Answer

The top answer is right  that the error code doesn t give you much info  One of the common causes that we saw in our team for this error code was when the query was not optimized well  A known reason was when we do an inner join with the left side table magnitudes bigger than the table on right side  Swapping these tables  would usually do the trick in such cases

User · Answer

I was also facing same error when I was inserting the data into HIVE external table which was pointing to Elastic search cluster   I replaced the older JAR elasticsearch-hadoop-2 0 0 RC1 jar to elasticsearch-hadoop-5 6 0 jar  and everything worked fine   My Suggestion is please use the specific JAR as per the elastic search version  Don t use older JARs if you are using newer version of elastic search   Thanks to this post Hive- Elasticsearch Write Operation  409

User · Answer

Adding some information here  as it took me awhile to find the hadoop jobtracker web-dashboard in HDInsight  Azure s Hadoop   and a colleague finally showed me where it was  There is a shortcut on the head node called  Hadoop Yarn Status  which is just a link to a local http page  http   headnodehost 9014 cluster in my case   When opened the dashboard looked like this     In that dashboard you can find your failed application  and then after clicking into it you can look at the logs of the individual map and reduce jobs   In my case it seemed to still be running out of memory in the reducers  even though I had cranked the memory in the configuration already  For some reason it was not surfacing the  java outofmemory  errors I got earlier though

User · Answer

I faced the same issue because I didn t have permission to query the database I was trying to   In the case you don t have permission to query the table database  besides the Return Code 2 from org apache hadoop hive ql exec MapRedTask error  you will see that in Cloudera Manager is not even registering your query

User · Answer

I know I am 3 years late on this thread  however still providing my 2 cents for similar cases in future   I recently faced the same issue error in my cluster  The JOB would always get to some 80   reduction and fail with the same error  with nothing to go on in the execution logs either  Upon multiple iterations and research I found that among the plethora of files getting loaded some were non-compliant with the structure provided for the base table table being used to insert data into partitioned table     Point to be noted here is whenever I executed a select query for a particular value in the partitioning column or created a static partition it worked fine as in that case error records were being skipped   TL DR  Check the incoming data files for inconsistency in the structuring as HIVE follows Schema-On-Read philosophy

User · Answer

Even I faced the same issue - when checked on dashboard I found following Error  As the data was coming through Flume and had interrupted in between due to which may be there was inconsistency in few files   Caused by  org apache hadoop hive serde2 SerDeException  org codehaus jackson JsonParseException  Unexpected end-of-input within between OBJECT entries   Running on fewer files it worked  Format consistency was the reason in  my case

User · Answer

I removed the  SUCCESS file from the EMR output path in S3 and it worked fine

User · Answer

That s not the real error  here s how to find it   Go to the hadoop jobtracker web-dashboard  find the hive mapreduce jobs that failed and look at the logs of the failed tasks  That will show you the real error    The console output errors are useless  largely beause it doesn t have a view of the individual jobs tasks to pull the real errors  there could be errors in multiple tasks   Hope that helps

[hadoop] What is Hive: Return Code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask

Examples related to hadoop

Examples related to mapreduce

Examples related to hive