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

Posted to common-user@hadoop.apache.org by Espen Amble Kolstad <es...@trank.no> on 2007/01/25 14:14:13 UTC

Unable to set mapred.tasktracker.tasks.maximum on different nodes in the cluster

Hi,

Is there any way to have some nodes in a cluster to have different 
mapred.tasktracker.tasks.maximum setting than others?
I can't seem to get this to work by changing conf/hadoop-site.xml on some of 
the nodes.

Your help is appreciated!

- Espen

Re: Unable to set mapred.tasktracker.tasks.maximum on different nodes in the cluster

Posted by Owen O'Malley <ow...@yahoo-inc.com>.

On Jan 25, 2007, at 5:14 AM, Espen Amble Kolstad wrote:

> Hi,
>
> Is there any way to have some nodes in a cluster to have different
> mapred.tasktracker.tasks.maximum setting than others?
> I can't seem to get this to work by changing conf/hadoop-site.xml  
> on some of
> the nodes.

In theory that should work, but currently the job tracker assumes  
mapred.tasktracker.tasks.maximum is constant across the entire  
cluster. It would be a reasonable issue/patch to remove that limitation.

-- Owen

Re: Unable to set mapred.tasktracker.tasks.maximum on different nodes in the cluster

Posted by Doug Cutting <cu...@apache.org>.

Espen Amble Kolstad wrote:
> Is there any way to have some nodes in a cluster to have different 
> mapred.tasktracker.tasks.maximum setting than others?
> I can't seem to get this to work by changing conf/hadoop-site.xml on some of 
> the nodes.

That should work, but perhaps the JobTracker bases task allocations on 
it's configured max, rather than summing the configured max of all 
tasktrackers.  If, on further inspection, that appears to be the case, 
please submit an issue in Jira.

Thanks,

Doug