You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2007/12/03 12:45:43 UTC

[jira] Updated: (HADOOP-2300) mapred.tasktracker.tasks.maximum is completely ignored

     [ https://issues.apache.org/jira/browse/HADOOP-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-2300:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Amareshwari!

> mapred.tasktracker.tasks.maximum is completely ignored
> ------------------------------------------------------
>
>                 Key: HADOOP-2300
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2300
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.16.0
>            Reporter: Owen O'Malley
>            Assignee: Amareshwari Sri Ramadasu
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: patch-2300.txt
>
>
> HADOOP-1274 replaced the configuration attribute mapred.tasktracker.tasks.maximum with mapred.tasktracker.map.tasks.maximum and mapred.tasktracker.reduce.tasks.maximum and claims to use the deprecated mapred.tasktracker.tasks.maximum. However, because the new attributes are in hadoop-default.xml, the check to use the deprecated value will never trigger.

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