[ 
https://issues.apache.org/jira/browse/HADOOP-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670575#action_12670575
 ] 

Nathan Marz commented on HADOOP-5160:
-------------------------------------

I am seeing this behavior on a cluster running version 0.18.1. This is a 16 
machine cluster and there are exactly 16 reducers. I tend to see 2 or 3 
machines idle during the reducing.

> Hadoop reduce scheduler sometimes leaves machines idle
> ------------------------------------------------------
>
>                 Key: HADOOP-5160
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5160
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Nathan Marz
>
> I have a MapReduce application with number of reducers equal to the number of 
> machines in the cluster (and with speculative execution turned off). However, 
> Hadoop schedules multiple reduces to run on single machines and leaves other 
> machines idle. This causes contention and seriously slows down the job. 
> Hadoop should employ the simple heuristic of utilizing as many machines as 
> possible when scheduling reduces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to