Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5FD0411A0E for ; Fri, 15 Aug 2014 01:07:05 +0000 (UTC) Received: (qmail 65625 invoked by uid 500); 15 Aug 2014 01:07:00 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 65485 invoked by uid 500); 15 Aug 2014 01:07:00 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 65475 invoked by uid 99); 15 Aug 2014 01:07:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Aug 2014 01:07:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of senshaw@gmail.com designates 209.85.213.171 as permitted sender) Received: from [209.85.213.171] (HELO mail-ig0-f171.google.com) (209.85.213.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Aug 2014 01:06:34 +0000 Received: by mail-ig0-f171.google.com with SMTP id l13so623560iga.4 for ; Thu, 14 Aug 2014 18:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jrO++cS9PL5rd2Jy7ZOxvUHapOcsUUOsgewCwoUsx5k=; b=yD203cM4z6mJQZA3YpEMWgzwfL5+9EWyWWIkBIgHh5vlALkZ3NA8Bw60CAGIF6IKA+ seBvfnJiG6VqZVlUOfB21wLH+Ig44HCZvEItGroDfJlu+Veq4XDxRQ7fScIg8l1h1xMA AdAbZYEhvTAf0wCPAk/AZRxaxTeKxWeuM4GLQjQxpv27TmHXzDqfQW7b2jcgn/+mbVDa CigC1bJgBurUP005Ptmoq0AWUhTras9PbYs22vRleabqkZK/dZLLbF3V5G1/9YoFRve/ LuIUpw8e5r87yB59OYkliW94scj52W9pmky2oQZ7rm0peO1xREsdr9hoI0FYvl5GXnqt YkrA== MIME-Version: 1.0 X-Received: by 10.42.58.210 with SMTP id j18mr18649995ich.2.1408064793407; Thu, 14 Aug 2014 18:06:33 -0700 (PDT) Received: by 10.107.161.203 with HTTP; Thu, 14 Aug 2014 18:06:33 -0700 (PDT) In-Reply-To: References: Date: Thu, 14 Aug 2014 18:06:33 -0700 Message-ID: Subject: Re: Hadoop 2.2 Built-in Counters From: ou senshaw To: user Content-Type: multipart/alternative; boundary=20cf30334b49d4f7ad0500a0a19c X-Virus-Checked: Checked by ClamAV on apache.org --20cf30334b49d4f7ad0500a0a19c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks guys! It's working. On Thu, Aug 14, 2014 at 2:39 AM, Chris MacKenzie < studio@chrismackenziephotography.co.uk> wrote: > Hi, > > This is the content of my shell script for running the job history server= : > > cd $HADOOP_PREFIX > hadoop fs -mkdir -p /mr-history/tmp > hadoop fs -chmod -R 1777 /mr-history/tmp > hadoop fs -mkdir -p /mr-history/done > hadoop fs -chmod -R 1777 /mr-history/done > > sbin/mr-jobhistory-daemon.sh start historyserver > > These configurable variables are in mapred-site.xml > > > mapreduce.jobhistory.address > 137.195.143.129:10020 > Default port is 10020. > > > > mapreduce.jobhistory.webapp.address > 137.195.143.129:19888 > Default port is 19888. > > > I start the history server on the same node as my resource manager > > > The counters are available from when the job is running from: > > http://your-server:8088/proxy/application_1408007466921_0002/mapreduce/jo= b/ > job_1408007466921_0002 > > Drill down through the application master to the job. > > If you don=C2=B9t have the history server running the job data is not > persistent. > > Hope this helps. > > > Regards, > > Chris MacKenzie > telephone: 0131 332 6967 > email: studio@chrismackenziephotography.co.uk > corporate: www.chrismackenziephotography.co.uk > > > > > > > > > > From: ou senshaw > Reply-To: > Date: Thursday, 14 August 2014 07:14 > To: > Subject: Hadoop 2.2 Built-in Counters > > > Hi all, > I'm trying to analyze my mapreduce job performance via built-in counters > such as physical memory usage, heap memory usage... > When the job is running, I can watch these counters via Resource manager > website(namenode:8088). However, when the job is done, counter informatio= n > is not available in resource manager website anymore. I know I can get > them from client output. I was wondering if there is other place in name > node or data node to get the final counter measures regarding job id? > Thanks, > Shaw > > > --20cf30334b49d4f7ad0500a0a19c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks guys! It's working.


On Thu, Aug 14, 2014 at 2:39 AM, Ch= ris MacKenzie <studio@chrismackenziephotography.co.uk= > wrote:
Hi,

This is the content of my shell script for running the job history server:<= br>
cd $HADOOP_PREFIX
hadoop fs -mkdir -p /mr-history/tmp
hadoop fs -chmod -R 1777 /mr-history/tmp
hadoop fs -mkdir -p /mr-history/done
hadoop fs -chmod -R 1777 /mr-history/done

sbin/mr-jobhistory-daemon.sh start historyserver

These configurable variables are in mapred-site.xml

<property>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <name>mapreduce.jobhistory.address</na= me>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <value>137.195.143.129:10020</value>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <description>Default port is 10020.</d= escription>
=C2=A0 =C2=A0 </property>

=C2=A0 =C2=A0 <property>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <name>mapreduce.jobhistory.webapp.address= </name>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <value>137.195.143.129:19888</value>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <description>Default port is 19888.</d= escription>
=C2=A0 =C2=A0 </property>

I start the history server on the same node as my resource manager


The counters are available from when the job is running from:

http://your-server:8088/proxy/app= lication_1408007466921_0002/mapreduce/job/
job_1408007466921_0002


Drill down through the application master to the job.

If you don=C2=B9t have the history server running the job data is not
persistent.

Hope this helps.


Regards,

Chris MacKenzie
telephone: 0131 332 6967
email: studio@chr= ismackenziephotography.co.uk
corporate: www.chrismackenziephotography.co.uk
<http://www.chrismackenziephotography.co.uk/>
<http://plus.google.com/+ChrismackenziephotographyCoUk/po= sts>
<http://www.linkedin.com/in/chrismackenziephotography/><= br>





From: =C2=A0ou senshaw <senshaw@gma= il.com>
Reply-To: =C2=A0<user@hadoop.a= pache.org>
Date: =C2=A0Thursday, 14 August 2014 07:14
To: =C2=A0<user@hadoop.apache.= org>
Subject: =C2=A0Hadoop 2.2 Built-in Counters


Hi all,
I'm trying to analyze my mapreduce job performance via built-in counter= s
such as physical memory usage, heap memory usage...
When the job is running, I can watch these counters via Resource manager website(namenode:8088). However, when the job is done, counter information<= br> is not available in resource manager website anymore. I know I can get
them from client output. I was wondering if there is other place in name node or data node to get the final counter measures regarding job id?
Thanks,
Shaw



--20cf30334b49d4f7ad0500a0a19c--