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

Todd Lipcon commented on MAPREDUCE-2905:
----------------------------------------

That's exactly the point. If the existing test didn't fail, even though there 
was a bug, then the existing test wasn't good enough. Hence you need to add a 
new test or improve the existing one in such a way that the test fails without 
this bug fix and passes with it.
                
> CapBasedLoadManager incorrectly allows assignment when assignMultiple is true 
> (was: assignmultiple per job)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2905
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2905
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/fair-share
>    Affects Versions: 0.20.2
>            Reporter: Jeff Bean
>         Attachments: MR-2905.patch, MR-2905.patch.2
>
>
> We encountered a situation where in the same cluster, large jobs benefit from 
> mapred.fairscheduler.assignmultiple, but small jobs with small numbers of 
> mappers do not: the mappers all clump to fully occupy just a few nodes, which 
> causes those nodes to saturate and bottleneck. The desired behavior is to 
> spread the job across more nodes so that a relatively small job doesn't 
> saturate any node in the cluster.
> Testing has shown that setting mapred.fairscheduler.assignmultiple to false 
> gives the desired behavior for small jobs, but is unnecessary for large jobs. 
> However, since this is a cluster-wide setting, we can't properly tune.
> It'd be nice if jobs can set a param similar to 
> mapred.fairscheduler.assignmultiple on submission to better control the task 
> distribution of a particular job.

--
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