[ 
https://issues.apache.org/jira/browse/HBASE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629515#comment-13629515
 ] 

Jonathan Hsieh commented on HBASE-8324:
---------------------------------------

Talked with [~sandyr], and we found this in the MRAppMaster's logs:

{code}
2013-04-11 14:29:30,234 INFO [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: 
attempt_1365715697057_0001_r_000001_1 TaskAttempt Transitioned from UNASSIGNED 
to KILLED
2013-04-11 14:29:30,234 INFO [Thread-47] 
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Processing the 
event EventType: CONTAINER_DEALLOCATE
2013-04-11 14:29:30,235 ERROR [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskImpl: Unexpected event for 
REDUCE task T_ATTEMPT_KILLED
2013-04-11 14:29:30,235 ERROR [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskImpl: Invalid event 
T_ATTEMPT_KILLED on Task task_1365715697057_0001_r_000001
2013-04-11 14:29:30,241 INFO [AsyncDispatcher event handler] 
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl: job_1365715697057_0001Job 
Transitioned from RUNNING to ERROR
2013-04-11 14:29:30,261 INFO [IPC Server handler 12 on 60014] 
org.apache.hadoop.mapred.TaskAttemptListenerImpl: Commit-pending state update 
from attempt_1365715697057_0001_r_000004_0
{code}

This is related to MAPREDUCE-4880 which is in turn fixed by MAPREDUCE-4607 (a 
race in speculative task execution, fixed in 2.0.3-alpha).  Compiling and 
running against hadoop-2.0.3-alpha fails out even earlier so instead of going 
that route, I'm going to try an alternate workaround -- disabling mapper and 
reducer speculative execution.
                
> TestHFileOutputFormat.testMRIncremental* fails against hadoop2 profile
> ----------------------------------------------------------------------
>
>                 Key: HBASE-8324
>                 URL: https://issues.apache.org/jira/browse/HBASE-8324
>             Project: HBase
>          Issue Type: Sub-task
>          Components: hadoop2, test
>    Affects Versions: 0.95.0
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>             Fix For: 0.95.1
>
>
> Two tests cases are failing:
> testMRIncrementalLoad, testMRIncrementalloadWithSplit
> {code}
> <testcase time="33.942" 
> classname="org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat" 
> name="testMRIncrementalLoad">
>     <failure type="java.lang.AssertionError">java.lang.AssertionError
>         at org.junit.Assert.fail(Assert.java:86)
>         at org.junit.Assert.assertTrue(Assert.java:41)
>         at org.junit.Assert.assertTrue(Assert.java:52)
>         at 
> org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.runIncrementalPELoad(TestHFileOutputFormat.java:468)
>         at 
> org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.doIncrementalLoadTest(TestHFileOutputFormat.java:378)
>         at 
> org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.testMRIncrementalLoad(TestHFileOutputFormat.java:348)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
>   <testcase time="34.324" 
> classname="org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat" 
> name="testMRIncrementalLoadWithSplit">
>     <failure type="java.lang.AssertionError">java.lang.AssertionError
>         at org.junit.Assert.fail(Assert.java:86)
>         at org.junit.Assert.assertTrue(Assert.java:41)
>         at org.junit.Assert.assertTrue(Assert.java:52)
>         at 
> org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.runIncrementalPELoad(TestHFileOutputFormat.java:468)
>         at 
> org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.doIncrementalLoadTest(TestHFileOutputFormat.java:378)
>         at 
> org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.testMRIncrementalLoadWithSplit(TestHFileOutputFormat.java:354)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         ...
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to