hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1274) Configuring different number of mappers and reducers per TaskTracker
Date Mon, 19 Nov 2007 18:07:46 GMT

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

Doug Cutting commented on HADOOP-1274:

> we really need HADOOP-2160 (documentation by releases) before we can start enforcing
this, correct?

Sigh.  I see your point.  If we commit the doc change to trunk and someone republishes the
website, from trunk, then the website documentation will document 0.16, which isn't yet released,
rather than 0.15, the current release.  We could use 'svn switch' on people.apache.org so
that the website is stuck on the 0.15 branch until we release 0.16, but that would prohibit
other changes to the website.  it sure would be nice to fix HADOOP-2160...

> 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