hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2495) Increase granularity of write operations in ReplicationMonitor thus reducing contention for write lock
Date Wed, 07 Mar 2012 09:39:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224142#comment-13224142

Hudson commented on HDFS-2495:

Integrated in Hadoop-Mapreduce-trunk-Commit #1855 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1855/])
    Moving HDFS-2158, HDFS-2188, HDFS-2334, HDFS-2477, HDFS-2495, HDFS-2476, HDFS-1580, HDFS-1765
to 0.23.3 section in CHANGES.txt (Revision 1297903)

     Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1297903
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

> Increase granularity of write operations in ReplicationMonitor thus reducing contention
for write lock
> ------------------------------------------------------------------------------------------------------
>                 Key: HDFS-2495
>                 URL: https://issues.apache.org/jira/browse/HDFS-2495
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Tomasz Nykiel
>            Assignee: Tomasz Nykiel
>             Fix For: 0.24.0, 0.23.3
>         Attachments: replicationMon.patch, replicationMon.patch-1
> For processing blocks in ReplicationMonitor (BlockManager.computeReplicationWork), we
first obtain a list of blocks to be replicated by calling chooseUnderReplicatedBlocks, and
then for each block which was found, we call computeReplicationWorkForBlock. The latter processes
a block in three stages, acquiring the writelock twice per call:
> 1. obtaining block related info (livenodes, srcnode, etc.) under lock
> 2. choosing target for replication
> 3. scheduling replication (under lock)
> We would like to change this behaviour and decrease contention for the write lock, by
batching blocks and executing 1,2,3, for sets of blocks, rather than for each one separately.
This would decrease the number of writeLock to 2, from 2*numberofblocks.
> Also, the info level logging can be pushed outside the writelock.

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


View raw message