[
https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990603#comment-14990603
]
Jason Lowe commented on YARN-570:
---------------------------------
So this changed timestamps to be rendered unconditionally in local time?
That's unfortunate. See [~aw]'s comment in
https://issues.apache.org/jira/browse/YARN-2348?focusedCommentId=14073218&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14073218.
Unfortunately local timezone isn't always the right thing to do because the
timestamps of the log files for tasks will _not_ be the local timezone of the
browser when running jobs in a distant colo. So this change makes it worse for
users that are lining up events based on what they see in the UI with what they
see in the logs.
This minimally should have been configurable. Filed YARN-4332 to either revert
this change or make it configurable.
> Time strings are formated in different timezone
> -----------------------------------------------
>
> Key: YARN-570
> URL: https://issues.apache.org/jira/browse/YARN-570
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
> Affects Versions: 2.2.0
> Reporter: Peng Zhang
> Assignee: Akira AJISAKA
> Fix For: 2.7.0
>
> Attachments: MAPREDUCE-5141.patch, YARN-570.2.patch,
> YARN-570.3.patch, YARN-570.4.patch, YARN-570.5.patch
>
>
> Time strings on different page are displayed in different timezone.
> If it is rendered by renderHadoopDate() in yarn.dt.plugins.js, it appears as
> "Wed, 10 Apr 2013 08:29:56 GMT"
> If it is formatted by format() in yarn.util.Times, it appears as "10-Apr-2013
> 16:29:56"
> Same value, but different timezone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
