[
https://issues.apache.org/jira/browse/MAPREDUCE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841746#action_12841746
]
Vinod K V commented on MAPREDUCE-1562:
--------------------------------------
Two things I immediately can identify:
- One TT crashed because of jetty port problem, possibly related to HADOOP-6528
{code}
[exec] [junit] 2010-03-04 09:40:24,493 ERROR mapred.TaskTracker
(TaskTracker.java:offerService(1460)) - Caught exception: java.io.IOException:
Jetty problem. Jetty didn't bind to a valid port
[exec] [junit] at
org.apache.hadoop.mapred.TaskTracker.checkJettyPort(TaskTracker.java:1276)
[exec] [junit] at
org.apache.hadoop.mapred.TaskTracker.offerService(TaskTracker.java:1438)
[exec] [junit] at
org.apache.hadoop.mapred.TaskTracker.run(TaskTracker.java:2256)
[exec] [junit] at
org.apache.hadoop.mapred.MiniMRCluster$TaskTrackerRunner.run(MiniMRCluster.java:228)
[exec] [junit] at java.lang.Thread.run(Thread.java:619)
{code}
I think we should fail *any* test immediately if MiniMRCluster fails to start
even a single TT.
- Two, I see this 15 min wait (!!)
{code}
else if(MAPPER_BAD_RECORDS.get(2).equals(str)) {
try {
LOG.warn("MAP Encountered BAD record");
Thread.sleep(15*60*1000);
} catch (InterruptedException e) {
e.printStackTrace();
}
}
{code}
Not sure why this is not causing the test to fail all the time.
> TestBadRecords fails sometimes
> ------------------------------
>
> Key: MAPREDUCE-1562
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1562
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Reporter: Vinod K V
> Fix For: 0.22.0
>
> Attachments: consoleText
>
>
> TestBadRecords.testMapRed fails sometimes. One instance of this was seen by
> Hudson while testing MAPREDUCE-890:
> http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/342/testReport/.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
