[
https://issues.apache.org/jira/browse/HDFS-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402634#comment-13402634
]
Hadoop QA commented on HDFS-3510:
---------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12533705/HDFS-3510.011.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2714//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2714//console
This message is automatically generated.
> Improve FSEditLog pre-allocation
> --------------------------------
>
> Key: HDFS-3510
> URL: https://issues.apache.org/jira/browse/HDFS-3510
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Fix For: 1.0.0, 2.0.1-alpha
>
> Attachments: HDFS-3510-b1.001.patch, HDFS-3510-b1.002.patch,
> HDFS-3510.001.patch, HDFS-3510.003.patch, HDFS-3510.004.patch,
> HDFS-3510.004.patch, HDFS-3510.006.patch, HDFS-3510.007.patch,
> HDFS-3510.008.patch, HDFS-3510.009.patch, HDFS-3510.010.patch,
> HDFS-3510.011.patch
>
>
> It is good to avoid running out of space in the middle of writing a batch of
> edits, because when it happens, we often get partial edits at the end of the
> log.
> Edit log preallocation can solve this problem (see HADOOP-2330 for a full
> description of edit log preallocation).
> The current pre-allocation code was introduced for performance reasons, not
> for preventing partial edits. As a consequence, we sometimes do a write
> without using pre-allocation. We should change the pre-allocation code so
> that it always preallocates at least enough space before writing out the
> edits.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
