hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thanh Do (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1222) NameNode fail stop in spite of multiple metadata directories
Date Sun, 20 Jun 2010 16:37:26 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880649#action_12880649
] 

Thanh Do commented on HDFS-1222:
--------------------------------

Triggering the rare cases is the goal of our project. 
We have read some papers saying that rare failure do happen,
and when they happen, the system does not behave as expected.
Thus, our view is that we should expect the unexpected.

> NameNode fail stop in spite of multiple metadata directories
> ------------------------------------------------------------
>
>                 Key: HDFS-1222
>                 URL: https://issues.apache.org/jira/browse/HDFS-1222
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.1
>            Reporter: Thanh Do
>
> Despite the ability to configure multiple name directories
> (to store fsimage) and edits directories, the NameNode will fail stop 
> in most of the time it faces exception when accessing to these directories.
>  
> NameNode fail stops if an exception happens when loading fsimage,
> reading fstime, loading edits log, writing fsimage.ckpt ..., although there 
> are still good replicas. NameNode could have tried to work with other replicas,
> and marked the faulty one.
> This bug was found by our Failure Testing Service framework:
> http://www.eecs.berkeley.edu/Pubs/TechRpts/2010/EECS-2010-98.html
> For questions, please email us: Thanh Do (thanhdo@cs.wisc.edu) and 
> Haryadi Gunawi (haryadi@eecs.berkeley.edu)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message