[
https://issues.apache.org/jira/browse/HDFS-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ming Ma updated HDFS-6722:
--------------------------
Attachment: HDFS-6722-2.patch
Thanks, Vinayakumar and Haohui. Here is the updated patch based on client side.
Please note that client side approach has these issues.
1. Client machine's local time zone could be different from the NN machine's
local time zone. On the NN webUI, the NN started up time comes from JMX and is
based on NN machine's local time zone. So there will be two time zones on the
webUI.
2. Data precision. LastContact JMX value is round to second unit by
FSNameSystem. So there is certain degree of data lost. At the client side, the
script uses Date.now() which return value in millisecond unit. So the end
result customers get on the webUI could change by 1 sec if they refresh the
web page.
> Display readable last contact time for dead nodes on NN webUI
> -------------------------------------------------------------
>
> Key: HDFS-6722
> URL: https://issues.apache.org/jira/browse/HDFS-6722
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ming Ma
> Assignee: Ming Ma
> Attachments: HDFS-6722-2.patch, HDFS-6722.patch
>
>
> For dead node info on NN webUI, admins want to know when the nodes became
> dead, to troubleshoot missing block, etc. Currently the webUI displays the
> last contact as "the unit of seconds since the last contact". It will be
> useful to display the info in Date format.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
