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

Mingliang Liu updated HDFS-9442:
--------------------------------
    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

As stated in the promising work in [HDFS-10419], the storage container layer 
provides an object storage interface and aims to manage data/metadata in a 
distributed manner. The motivation and value of this work will not stand after 
that.

Considering the incomplete and inactive status of this work, resolving it as 
"won't fix".

> 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, 
> HDFS-9442.005.patch, HDFS-9442.006.patch, HDFS-9442.007.patch, 
> HDFS-9442.008.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)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to