[
https://issues.apache.org/jira/browse/HADOOP-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625568#action_12625568
]
dhruba borthakur commented on HADOOP-2330:
------------------------------------------
This test failure is note related to this patch, it has been occuring in other
tests as well, see
https://issues.apache.org/jira/browse/HADOOP-3954?focusedCommentId=12624974#action_12624974.
I am going to commit this patch tonight.
> 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.
