hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-93) NameNode should not serve up a bad edits log
Date Thu, 29 Dec 2011 13:25:31 GMT

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

Harsh J resolved HDFS-93.
-------------------------

    Resolution: Cannot Reproduce

This isn't a problem in the current version anymore. Errors in the dfs.namenode.name.dirs
are well handled, and omitted out.
                
> NameNode should not serve up a bad edits log
> --------------------------------------------
>
>                 Key: HDFS-93
>                 URL: https://issues.apache.org/jira/browse/HDFS-93
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Robert Chansler
>
> A NameNode disk failure (apparently) resulted in the NameNode serving a bad edits log
to the Secondary NameNode. The SNN observed the problem (good!), but had no alternative but
to ask again for the log, and again get the same bad replica.
> 1. The NN could/should have observed the same fault as the SNN.
> 2. If a replica is known to be bad, the NN should serve a different replica, if available.
> 3. The SNN should have a way to report replica failure to the NN.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message