hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Lamb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8214) Secondary NN Web UI shows wrong date for Last Checkpoint
Date Fri, 24 Apr 2015 06:46:39 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Charles Lamb updated HDFS-8214:
-------------------------------
    Attachment: HDFS-8214.001.patch

[~yzhang], could you please take a look at this?

We could either try to have Last Checkpoint: be a relative time (e.g. "26 secs ago" as the
current SecondaryNameNode#toString does, or we could have it be a wallclock time. Unfortunately,
having it be a relative time means that the JS for secondary/status.html would have to compute
that in the brower client's local TZ which is problematic. In fact, Start Time is already
in wallclock time so it feels best to mimic that. This does, however, mean that the #toString
method has to be changed (back) to have Last Checkpoint be a wallclock time rather than the
relative time that HDFS-5591 changed it to be.

> Secondary NN Web UI shows wrong date for Last Checkpoint
> --------------------------------------------------------
>
>                 Key: HDFS-8214
>                 URL: https://issues.apache.org/jira/browse/HDFS-8214
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: HDFS, namenode
>    Affects Versions: 2.7.0
>            Reporter: Charles Lamb
>            Assignee: Charles Lamb
>         Attachments: HDFS-8214.001.patch
>
>
> SecondaryNamenode is using Time.monotonicNow() to display Last Checkpoint in the web
UI. This causes weird times, generally, just after the epoch, to be displayed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message