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 "Sameer Paranjpye (JIRA)" <ji...@apache.org> on 2007/06/27 19:13:26 UTC

[jira] Updated: (HADOOP-1245) value for mapred.tasktracker.tasks.maximum taken from two different sources

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

Sameer Paranjpye updated HADOOP-1245:
-------------------------------------

    Component/s: mapred

> value for mapred.tasktracker.tasks.maximum taken from two different sources
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-1245
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1245
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.12.3
>            Reporter: Michael Bieniosek
>
> When I start a job, hadoop uses mapred.tasktracker.tasks.maximum on the jobtracker.  Once these tasks finish, it is the tasktracker's value of mapred.tasktracker.tasks.maximum that decides how many new tasks are created for each host. 
> This would probably be fixed if HADOOP-785 were implemented.

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