[
https://issues.apache.org/jira/browse/HADOOP-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618612#action_12618612
]
Hadoop QA commented on HADOOP-3864:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12387251/HADOOP-3864_0_20080830.patch
against trunk revision 681243.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+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 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2991/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2991/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2991/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2991/console
This message is automatically generated.
> JobTracker lockup due to JobInProgress.initTasks taking significant time for
> large jobs on large clusters
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3864
> URL: https://issues.apache.org/jira/browse/HADOOP-3864
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Priority: Critical
> Fix For: 0.19.0
>
> Attachments: HADOOP-3864_0_20080830.patch
>
>
> JobInProgress.initTasks takes significant amount of time on a large cluster
> for large jobs (55k maps * 3 splits), during which the JobInProgress object
> is locked up.
> Simultaneously the JobClient is calling JobTracker.getTaskCompletionEvents
> which locks the JobTracker & tries to lock the JobInProgress, there-by it
> starves all heartbeats which are trying to lock the JobTracker - resulting in
> a lockup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
