[
https://issues.apache.org/jira/browse/HDFS-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455300#comment-13455300
]
Kihwal Lee commented on HDFS-3922:
----------------------------------
I manually ran test-patch for 0.23. There were actually no additional javadoc
warnings introduced by the patch.
{noformat}
-1 overall.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 7 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version )
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
{noformat}
> 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
> 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
