hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5443) Namenode can stuck in safemode on restart if it crashes just after addblock logsync and after taking snapshot for such file.
Date Tue, 05 Nov 2013 07:09:19 GMT

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

Uma Maheswara Rao G commented on HDFS-5443:
-------------------------------------------

Thanks Jing and Sathish.  If we delete dir deep in the tree, they are just noramal INode*,
so flow goes in diff path, where we are not wiping out on some conditions. Thanks Sathish
for digging into it. 
I don't think separate Jira is needed, as this JIRA mainly talks about that 0-sized blocks
wiping out. If you have test please post here.

> Namenode can stuck in safemode on restart if it crashes just after addblock logsync and
after taking snapshot for such file.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5443
>                 URL: https://issues.apache.org/jira/browse/HDFS-5443
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: snapshots
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Uma Maheswara Rao G
>            Assignee: sathish
>
> This issue is reported by Prakash and Sathish.
> On looking into the issue following things are happening.
> .
> 1) Client added block at NN and just did logsync
>    So, NN has block ID persisted.
> 2)Before returning addblock response to client take a snapshot for root or parent directories
for that file
> 3) Delete parent directory for that file
> 4) Now crash the NN with out responding success to client for that addBlock call
> Now on restart of the Namenode, it will stuck in safemode.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message