hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5124) A few optimizations to FsNamesystem#RecentInvalidateSets
Date Fri, 06 Feb 2009 23:16:59 GMT

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

Tsz Wo (Nicholas), SZE updated HADOOP-5124:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I committed this.  Thanks, Hairong!

> A few optimizations to FsNamesystem#RecentInvalidateSets
> --------------------------------------------------------
>                 Key: HADOOP-5124
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5124
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.21.0
>         Attachments: optimizeInvalidate.patch, optimizeInvalidate1.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.

View raw message