Return-Path: 
 <mapreduce-user-return-598-apmail-hadoop-mapreduce-user-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org
Received: (qmail 38703 invoked from network); 17 May 2010 13:09:51 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 17 May 2010 13:09:51 -0000
Received: (qmail 24677 invoked by uid 500); 17 May 2010 13:09:51 -0000
Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org
Received: (qmail 24635 invoked by uid 500); 17 May 2010 13:09:51 -0000
Mailing-List: contact mapreduce-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-user@hadoop.apache.org>
List-Id: <mapreduce-user.hadoop.apache.org>
Reply-To: mapreduce-user@hadoop.apache.org
Delivered-To: mailing list mapreduce-user@hadoop.apache.org
Received: (qmail 24627 invoked by uid 99); 17 May 2010 13:09:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 May 2010 13:09:51 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of james.hammerton@mendeley.com
 designates 209.85.161.48 as permitted sender)
Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 May 2010 13:09:45 +0000
Received: by fxm11 with SMTP id 11so1191582fxm.35
        for <mapreduce-user@hadoop.apache.org>;
 Mon, 17 May 2010 06:09:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.22.79 with SMTP id m15mr17397bkb.80.1274101763781;
 Mon, 17
	May 2010 06:09:23 -0700 (PDT)
Received: by 10.204.4.145 with HTTP; Mon, 17 May 2010 06:09:23 -0700 (PDT)
In-Reply-To: <AANLkTinCklcrttH9aWuq3_bxzAxKXlSzh-5OE3UFev9s@mail.gmail.com>
References: <AANLkTilZ8OGWCJHNMJzKgWlGshm_BLmQBm8rsiDneEH-@mail.gmail.com>
	 <AANLkTinCklcrttH9aWuq3_bxzAxKXlSzh-5OE3UFev9s@mail.gmail.com>
Date: Mon, 17 May 2010 14:09:23 +0100
Message-ID: <AANLkTik8JiQysRwJHPdygb2W1u2Rz18LYjwObqkfZ-sO@mail.gmail.com>
Subject: Re: Incorrect dates on job tracker history
From: James Hammerton <james.hammerton@mendeley.com>
To: mapreduce-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=00032555426209b6fe0486c9ef3a
X-Virus-Checked: Checked by ClamAV on apache.org

--00032555426209b6fe0486c9ef3a
Content-Type: text/plain; charset=ISO-8859-1

Version: 0.20.1+169.68

Regards,

James

On Mon, May 17, 2010 at 1:55 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> Which version of hadoop are you using ?
>
> Thanks
>
> On Monday, May 17, 2010, James Hammerton <james.hammerton@mendeley.com>
> wrote:
> > Hi,
> >
> > According to the job tracker history viewer on our Hadoop setup, all of
> our recent jobs were run on Wed May 05 15:58:58 UTC 2010. When you click on
> the individual jobs you get the correct times at which they ran. In fact,
> the history viewer seems to allocate the date at which the job tracker was
> (re)started  to all jobs run since the restart.
> >
> > Is this a bug or a config issue?
> >
> > James
> > --
> > James Hammerton | Senior Data Mining Engineer
> > www.mendeley.com/profiles/james-hammerton
> >
> > Mendeley Limited | London, UK | www.mendeley.com
> > Registered in England and Wales | Company Number 6419015
> >
> >
> >
> >
>



-- 
James Hammerton | Senior Data Mining Engineer
www.mendeley.com/profiles/james-hammerton

Mendeley Limited | London, UK | www.mendeley.com
Registered in England and Wales | Company Number 6419015

--00032555426209b6fe0486c9ef3a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Version: 0.20.1+169.68<br><br>Regards,<br><br>James<br><br><div class=3D"gm=
ail_quote">On Mon, May 17, 2010 at 1:55 PM, Ted Yu <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:yuzhihong@gmail.com">yuzhihong@gmail.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Which version of =
hadoop are you using ?<br>
<br>
Thanks<br>
<div><div></div><div class=3D"h5"><br>
On Monday, May 17, 2010, James Hammerton &lt;<a href=3D"mailto:james.hammer=
ton@mendeley.com">james.hammerton@mendeley.com</a>&gt; wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; According to the job tracker history viewer on our Hadoop setup, all o=
f our recent jobs were run on Wed May 05 15:58:58 UTC 2010. When you click =
on the individual jobs you get the correct times at which they ran. In fact=
, the history viewer seems to allocate the date at which the job tracker wa=
s (re)started=A0 to all jobs run since the restart.<br>

&gt;<br>
&gt; Is this a bug or a config issue?<br>
&gt;<br>
&gt; James<br>
&gt; --<br>
&gt; James Hammerton | Senior Data Mining Engineer<br>
&gt; <a href=3D"http://www.mendeley.com/profiles/james-hammerton" target=3D=
"_blank">www.mendeley.com/profiles/james-hammerton</a><br>
&gt;<br>
&gt; Mendeley Limited | London, UK | <a href=3D"http://www.mendeley.com" ta=
rget=3D"_blank">www.mendeley.com</a><br>
&gt; Registered in England and Wales | Company Number 6419015<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>James Hamme=
rton | Senior Data Mining Engineer<br><a href=3D"http://www.mendeley.com/pr=
ofiles/james-hammerton">www.mendeley.com/profiles/james-hammerton</a><br><b=
r>
Mendeley Limited | London, UK | <a href=3D"http://www.mendeley.com">www.men=
deley.com</a><br>Registered in England and Wales | Company Number 6419015<b=
r><br><br><br>

--00032555426209b6fe0486c9ef3a--