hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5443) Delete 0-sized block when deleting an under-construction file that is included in snapshot
Date Thu, 07 Nov 2013 18:49:17 GMT

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

Hudson commented on HDFS-5443:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #4701 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4701/])
HDFS-5443. Delete 0-sized block when deleting an under-construction file that is included
in snapshot. Contributed by Jing Zhao. (jing9: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1539754)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockInfoUnderConstruction.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/INodeFileUnderConstruction.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/snapshot/TestSnapshotBlocksMap.java


> Delete 0-sized block when deleting an under-construction file that is included in snapshot
> ------------------------------------------------------------------------------------------
>
>                 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: Jing Zhao
>             Fix For: 2.3.0
>
>         Attachments: 5443-test.patch, HDFS-5443.000.patch
>
>
> Namenode can stuck in safemode on restart if it crashes just after addblock logsync and
after taking snapshot for such file. 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