You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Mingliang Liu (JIRA)" <ji...@apache.org> on 2015/12/01 01:57:10 UTC

[jira] [Updated] (HDFS-9442) Move block replication logic from BlockManager to a new class ReplicationManager

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

Mingliang Liu updated HDFS-9442:
--------------------------------
    Attachment: HDFS-9442.004.patch

Per offline discussion with [~wheat9] and [~jingzhao], the v4 patch makes the {{ReplicationManager#removeBlockFromExcessReplicateMap()}} and {{ReplicationManager#isBlockExcessOnNode}} accept {{BlockInfo}} object instead of {{Block}}. This patch cherry picked [HDFS-9485].

> Move block replication logic from BlockManager to a new class ReplicationManager
> --------------------------------------------------------------------------------
>
>                 Key: HDFS-9442
>                 URL: https://issues.apache.org/jira/browse/HDFS-9442
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>         Attachments: HDFS-9442.000.patch, HDFS-9442.001.patch, HDFS-9442.002.patch, HDFS-9442.003.patch, HDFS-9442.004.patch
>
>
> Currently the {{BlockManager}} is managing all replication logic for over- , under- and mis-replicated blocks. This jira proposes to move that code to a new class named {{ReplicationManager}} for cleaner code logic, shorter source files, and easier lock separating work in future.
> The {{ReplicationManager}} is a package local class, providing {{BlockManager}} with methods that accesses its internal data structures of replication queue. Meanwhile, the class maintains the lifecycle of {{replicationThread}} and {{replicationQueuesInitializer}} daemon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)