[
https://issues.apache.org/jira/browse/HADOOP-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513012
]
Hadoop QA commented on HADOOP-1613:
-----------------------------------
-1, could not apply patch.
The patch command could not apply the latest attachment
http://issues.apache.org/jira/secure/attachment/12361868/lastContactTime.patch
as a patch to trunk revision r556707.
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/418/console
Please note that this message is automatically generated and may represent a
problem with the automation system and not the patch.
> The dfs webui (dfshealth) shows "Last Contact" as a negative number
> -------------------------------------------------------------------
>
> Key: HADOOP-1613
> URL: https://issues.apache.org/jira/browse/HADOOP-1613
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Priority: Minor
> Fix For: 0.14.0
>
> Attachments: lastContactTime.patch
>
>
> The dfshealth.jsp displays the number of seconds that have elapse since the
> namenode got a heartbeat from a datanode. When the number of nodes in the
> cluster are huge, may of these values are seen to be negative numbers.
> The FSNamesystem returns the timestamp when the namenode had last-heard from
> a datanode. The dfshealth.jsp gets the current system time and then subtracts
> the timestamp returned by the Namenode. This ordering of retrieving
> timestamps cause this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
