hadoop-hdfs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashwat Shriparv" <dwivedishash...@gmail.com>
Subject RE: Relevance of mapreduce.* configuration properties for MR V2
Date Sat, 18 Aug 2012 14:50:46 GMT
What is content of your /etc/hosts file?

 

From: rahul p [mailto:rahulpoolanchalil@gmail.com] 
Sent: Saturday, August 18, 2012 4:49 PM
To: user@hadoop.apache.org
Subject: Re: Relevance of mapreduce.* configuration properties for MR V2

 

Hi,

When i give bin/start-fs all 

namenode s not coming up..

On Fri, Aug 17, 2012 at 12:28 AM, mg <userformailinglists@gmail.com
<mailto:userformailinglists@gmail.com> > 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

 


Mime
View raw message