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] [Created] (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, 29 Oct 2013 18:40:27 GMT
Uma Maheswara Rao G created HDFS-5443:
-----------------------------------------

             Summary: 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: 2.2.0, 3.0.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