hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1274) Configuring different number of mappers and reducers per TaskTracker
Date Sat, 17 Nov 2007 07:22:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543261

Arun C Murthy commented on HADOOP-1274:

bq. Why shouldn't that be included with this patch? I think updating documentation in the
same commit as APIs are changed is appropriate.

I completely agree in principle. However we really need HADOOP-2160 (documentation by releases)
before we can start enforcing this, correct?

Specifically this patch deprecates  -{{mapred.tasktracker.tasks.maximum}}- and adds {{mapred.tasktracker.map.tasks.maximum}}
and {{mapred.tasktracker.reduce.tasks.maximum}} for 0.16.0.

> Configuring different number of mappers and reducers per TaskTracker
> --------------------------------------------------------------------
>                 Key: HADOOP-1274
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1274
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Koji Noguchi
>            Assignee: Amareshwari Sri Ramadasu
>             Fix For: 0.16.0
>         Attachments: patch-1274.txt, patch-1274.txt, patch-1274.txt, patch-1274.txt,
patch-1274.txt, patch-1274.txt
> Depending on the application, it sometimes make sense to have more mappers than reducers
assigned to each node. 
> (I'm assuming user either has a dedicated cluster or use HOD.)

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

View raw message