Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # user >> Relevance of mapreduce.* configuration properties for MR V2


Copy link to this message
-
Re: Relevance of mapreduce.* configuration properties for MR V2
Hi,

AFAIK, these properties are being ignored by YARN:
- mapreduce.tasktracker.map.tasks.maximum,
- mapreduce.tasktracker.reduce.tasks.maximum

Thanks,
Anil Gupta
On Thu, Aug 16, 2012 at 9:28 AM, mg <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I am currently trying to tune a CDH 4.0.1 (i~ hadoop 2.0.0-alpha) cluster
> running HDFS, YARN, and HBase managed by Cloudera Manager 4.0.3 (Free
> Edition).
>
>
> In CM, there are a number of options for setting mapreduce.* configuration
> properties on the YARN client page.
>
> Some of the properties and their explanations in the GUI still refer to
> JobTracker and TaskTracker, e.g.,
>
> - mapreduce.jobtracker.handler.**count,
> - mapreduce.tasktracker.map.**tasks.maximum,
> - mapreduce.tasktracker.reduce.**tasks.maximum
>
> I wonder whether these and a number of other mapreduce.* (e.g.,
> mapreduce.job.reduces) properties are observed by the MR2 ApplicationMaster
> (and how), or not.
>
>
> Can anyone clarify or point to respective documentation?
>
> Thanks,
> Martin
>

--
Thanks & Regards,
Anil Gupta