hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5015) Seprate block/replica management code from FSNamesystem
Date Fri, 01 May 2009 22:37:30 GMT

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

Suresh Srinivas updated HADOOP-5015:

    Attachment: blkmanager.patch

As a first step towards separating out block management functionality from FSNamesystem.java,
I have introduced a new class BlockManager.java. This new class is to be only used by {{FSNamesystem}},
using the synchronization as it exists today. To make code review simpler, I have also retained
the structure of the code moved from FSNamesystem.java as it is in BlockManager.java. After
this change, we could have more iterations to organize the code better with in BlockManager.java.

> Seprate block/replica management code from FSNamesystem
> -------------------------------------------------------
>                 Key: HADOOP-5015
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5015
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Hairong Kuang
>             Fix For: 0.21.0
>         Attachments: blkmanager.patch
> Currently FSNamesystem contains a big amount of code that manages blocks and replicas.
The code scatters in FSNamesystem and it is hard to read and maintain. It would be nice to
move the code to a separate class called, for example, BlockManager. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message