[
https://issues.apache.org/jira/browse/HDFS-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511498#comment-14511498
]
Andrew Wang commented on HDFS-8214:
-----------------------------------
Hi Charles,
This change basically makes sense. We were too zealous when we changed
getLastCheckpointTime(), that needs to still be a wallclock time for
compatibility purposes.
However, we have the option of displaying both the wallclock and the relative
time in the 2NN's toString. On the webUI, if we expose the relative time via a
new MXBean method, we can again display both.
> 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)
