hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-5124) A few optimizations to FsNamesystem#RecentInvalidateSets
Date Mon, 07 Nov 2011 22:04:51 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jitendra Nath Pandey updated HADOOP-5124:

    Attachment: HADOOP-5124-branch-0.20-security.patch

Patch for branch-0.20-security.
> 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: HADOOP-5124-branch-0.20-security.patch, 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.
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