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

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2014/06/23 22:52:25 UTC

[jira] [Commented] (MAPREDUCE-5939) StartTime showing up as the epoch time in JHS UI after upgrade

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041292#comment-14041292 ] 

Jason Lowe commented on MAPREDUCE-5939:
---------------------------------------

Appears to have been caused by MAPREDUCE-5052.  The job start time was added to the jhist name format but the parsing behavior when that new field is missing doesn't match the old behavior before it was added.

> StartTime showing up as the epoch time in JHS UI after upgrade
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-5939
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5939
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Kihwal Lee
>
> After upgrading from 0.23.x to 2.5, the start time of old apps are showing up as the epoch time.  It looks like 2.5 expects start time to be encoded at the end of the jhist file name (....xxxx-[timestamp].jhist). It should have been made backward compatible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)