hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4919) All maps hangs when set mapreduce.task.io.sort.factor to 1
Date Tue, 10 Mar 2015 07:12:38 GMT

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

Hadoop QA commented on MAPREDUCE-4919:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12563721/MAPREDUCE-4919.patch
  against trunk revision 47f7f18.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:

                  org.apache.hadoop.mapred.TestLineRecordReader
                  org.apache.hadoop.mapreduce.lib.input.TestLineRecordReader
                  org.apache.hadoop.mapred.TestMRTimelineEventHandling
                  org.apache.hadoop.mapred.TestLazyOutput
                  org.apache.hadoop.mapreduce.v2.TestMROldApiJobs

                                      The following test timeouts occurred in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:

org.apache.hadoop.mapreduce.lib.output.TestJobTests
org.apache.hadoop.mapred.TestMRIntermediateDataEncryption
org.apache.hadoop.mapred.TestMRIntermediateDataEncryption

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5261//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5261//console

This message is automatically generated.

> All maps hangs when set mapreduce.task.io.sort.factor to 1
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-4919
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4919
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>            Reporter: Jerry Chen
>            Assignee: Jerry Chen
>         Attachments: MAPREDUCE-4919.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> In one of my testing that when I set mapreduce.task.io.sort.factor to 1, all the maps
hang and will never end. But the CPU usage for each node are very high and until killed by
the app master when time out comes, and the job failed. 
> I traced the problem and found out that all the maps hangs on the final merge phase.
> The while loop in computeBytesInMerges will never end with a factor of 1:
> int f = 1; //in my case
> int n = 16; //in my case
> while (n > f || considerFinalMerge) {
>   ...
>   n -= (f-1);
>   f = factor;
> }
> As the f-1 will equals 0 and n will always be 16 and the while runs for ever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message