You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/07/16 08:15:05 UTC

[jira] Updated: (HADOOP-1613) The dfs webui (dfshealth) shows "Last Contact" as a negative number

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

dhruba borthakur updated HADOOP-1613:
-------------------------------------

    Status: Patch Available  (was: Open)

> 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
>         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.