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

Hudson commented on HDFS-3922:
------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #388 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/388/])
    HDFS-3922. namenode throws away blocks under construction on restart 
(Kihwal Lee via daryn) (Revision 1391150)

     Result = UNSTABLE
daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1391150
Files : 
* 
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogLoader.java
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSEditLogLoader.java

                
> 0.22 and 0.23 namenode throws away blocks under construction on restart
> -----------------------------------------------------------------------
>
>                 Key: HDFS-3922
>                 URL: https://issues.apache.org/jira/browse/HDFS-3922
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.1, 0.23.3
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>            Priority: Critical
>             Fix For: 0.23.4
>
>         Attachments: hdfs-3922.branch-023.patch.txt
>
>
> When reading edits on startup, namenode may throw away blocks under 
> construction. This is because the file inode is turned into a "under 
> construction" one, but nothing is done to the last block. 
> With append/hsync, this is not acceptable because it may drop sync'ed partial 
> blocks.  In branch 2 and trunk, HDFS-1623 (HA) fixed this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to