You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jeff Whiting (JIRA)" <ji...@apache.org> on 2010/06/03 17:50:56 UTC
[jira] Updated: (HADOOP-5124) A few optimizations to
FsNamesystem#RecentInvalidateSets
[ https://issues.apache.org/jira/browse/HADOOP-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Whiting updated HADOOP-5124:
---------------------------------
Attachment: optimizeInvalidate2-0.20.2.patch
I needed this in the 0.20.2 branch and created a patch for it. I thought it might be useful for others.
> A few optimizations to FsNamesystem#RecentInvalidateSets
> --------------------------------------------------------
>
> Key: HADOOP-5124
> URL: https://issues.apache.org/jira/browse/HADOOP-5124
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.21.0
>
> Attachments: optimizeInvalidate.patch, optimizeInvalidate1.patch, optimizeInvalidate2-0.20.2.patch, optimizeInvalidate2.patch
>
>
> This jira proposes a few optimization to FsNamesystem#RecentInvalidateSets:
> 1. when removing all replicas of a block, it does not traverse all nodes in the map. Instead it traverse only the nodes that the block is located.
> 2. When dispatching blocks to datanodes in ReplicationMonitor. It randomly chooses a predefined number of datanodes and dispatches blocks to those datanodes. This strategy provides fairness to all datanodes. The current strategy always starts from the first datanode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.