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

Jason Lowe commented on MAPREDUCE-4228:
---------------------------------------

The javadoc warnings are unrelated.  Not sure why findbugs failed, as it ran 
just fine for me locally (and on the first patch version).  Output from my 
local run:

-1 overall.  

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test 
files.

    -1 javadoc.  The javadoc tool appears to have generated 2 warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version ) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

                
> mapreduce.job.reduce.slowstart.completedmaps is not working properly to delay 
> the scheduling of the reduce tasks
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4228
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4228
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster, mrv2
>    Affects Versions: 0.23.1
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: MAPREDUCE-4228.patch, MAPREDUCE-4228.patch
>
>
> If no more map tasks need to be scheduled but not all have completed, the 
> ApplicationMaster will start scheduling reducers even if the number of 
> completed maps has not met the mapreduce.job.reduce.slowstart.completedmaps 
> threshold.  For example, if the property is set to 1.0 all maps should 
> complete before any reducers are scheduled.  However the reducers are 
> scheduled as soon as the last map task is assigned to a container.  For a job 
> with very long-running maps, a cluster with enough capacity to launch all map 
> tasks could cause reducers to launch prematurely and waste cluster resources.
> Thanks to Phil Su for discovering this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to