hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1879) disambiguate "datanode dead" vs "datanode heartbeat expired"
Date Mon, 22 Aug 2011 18:37:31 GMT

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

Matt Foley updated HDFS-1879:
-----------------------------

    Affects Version/s: 0.20.204.0

Since HDFS-1541 was committed to 0.20-security in time for 0.20.204 release, this bug should
also be fixed in 0.20-security.

> disambiguate "datanode dead" vs "datanode heartbeat expired"
> ------------------------------------------------------------
>
>                 Key: HDFS-1879
>                 URL: https://issues.apache.org/jira/browse/HDFS-1879
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.20.204.0, 0.23.0
>            Reporter: Matt Foley
>            Priority: Minor
>
> HDFS-1541 changed FSNamesystem.heartbeatCheck() so it would not call removeDatanode()
while the name system is in Safe Mode.  However, calls to FSNamesystem.isDatanodeDead() still
show datanodes as dead if their heartbeat is expired, so the Namenode status web page is not
consistent with the intent of HDFS-1541.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message