[
https://issues.apache.org/jira/browse/HADOOP-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690099#action_12690099
]
Hadoop QA commented on HADOOP-5337:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12403695/HADOOP-5337-v1.11.patch
against trunk revision 759030.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 12 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/149/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/149/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/149/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/149/console
This message is automatically generated.
> JobTracker greedily schedules tasks without running tasks to join
> -----------------------------------------------------------------
>
> Key: HADOOP-5337
> URL: https://issues.apache.org/jira/browse/HADOOP-5337
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Karam Singh
> Assignee: Amar Kamat
> Attachments: HADOOP-5337-v1.11.patch, HADOOP-5337-v1.7.patch,
> HADOOP-5337-v1.9.patch
>
>
> This issue was observed when JobTracker was restarted 3 times and observed
> that 4 instances of each reduce task were running. This issue is observed
> when cluster is not fully occupied.
> In testcase: Map/reduces capacity is 200/200 slots respectively and Job
> profile is 11000 maps, 10 reduces and speculative execution is off.
> JobTracker was restarted 3 times in small intervals of about 5 mins and after
> recovery, 40 reduce tasks were running. Task details web page
> (taskdetails.jsp) was showing 4 running attempts of each reduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
