[
https://issues.apache.org/jira/browse/HADOOP-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625543#action_12625543
]
Hadoop QA commented on HADOOP-2330:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12388699/preallocateTransactionLog4.patch
against trunk revision 688101.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3096/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3096/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3096/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3096/console
This message is automatically generated.
> Preallocate transaction log to improve namenode transaction logging
> performance
> -------------------------------------------------------------------------------
>
> Key: HADOOP-2330
> URL: https://issues.apache.org/jira/browse/HADOOP-2330
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.17.2
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.19.0
>
> Attachments: preallocateTransactionLog.patch,
> preallocateTransactionLog.patch, preallocateTransactionLog2.patch,
> preallocateTransactionLog3.patch, preallocateTransactionLog4.patch
>
>
> In the current implementation, the transaction log is opened in "append" mode
> and every new transaction is written to the end of the log. This means that
> new blocks get allocated to the edits file frequently.
> It is worth measuring the performance improvement when big chunks of the
> transaction log are allocated up front. Adding new transactions do not cause
> frequent block allocations for the edits log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
