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

Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/02/06 05:45:13 UTC

[jira] [Updated] (AMBARI-1344) mapred.tasktracker.reduce.tasks.maximum in mapred-site.xml is not taking effect

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

Yusaku Sako updated AMBARI-1344:
--------------------------------

    Summary: mapred.tasktracker.reduce.tasks.maximum in mapred-site.xml is not taking effect  (was: Incorrect option spelling in mapred-site.xml deployed by Ambari)
    
> mapred.tasktracker.reduce.tasks.maximum in mapred-site.xml is not taking effect
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-1344
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1344
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Pramod Thangali
>            Assignee: Yusaku Sako
>            Priority: Critical
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1344.patch
>
>
> Parameter name spelled incorrectly in mapred-site.xml (incorrect name stored in Postgres):
> Should be:
> root@bimota ambari-agent# cat /etc/hadoop/conf/mapred-site.xml | grep mapred.tasktracker.reduce.tasks.maximum
> Actually:
> root@bimota ambari-agent# cat /etc/hadoop/conf/mapred-site.xml | grep mapred.tasktracker.red.tasks.maximum
> <name>mapred.tasktracker.red.tasks.maximum</name>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira