hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2330) Preallocate transaction log to improve namenode transaction logging performance
Date Wed, 27 Aug 2008 00:56:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625926#action_12625926
] 

Raghu Angadi commented on HADOOP-2330:
--------------------------------------


The committed patch seems to have multiple debug logging left it. I think these should be
fixed (search for XXX or System in the patch).


> 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.


Mime
View raw message