[ 
https://issues.apache.org/jira/browse/HDFS-8697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609004#comment-14609004
 ] 

Andrew Wang commented on HDFS-8697:
-----------------------------------

Hmm. For EC I figured we would want to wait for expected rather than min 
replication, since reconstruction is much more expensive than just replicating. 
It also seems more dangerous for EC since losing that last block can result in 
more than one block of data loss.

Regarding naming, I'm happy to wait for HDFS-7955 for bigger renames. Cleaning 
up DecomManager now would be good (as I believe you plan to do) since we're 
already modifying it.

> Refactor DecommissionManager: more generic method names and misc cleanup
> ------------------------------------------------------------------------
>
>                 Key: HDFS-8697
>                 URL: https://issues.apache.org/jira/browse/HDFS-8697
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: namenode
>    Affects Versions: 2.7.0
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-8697.00.patch
>
>
> This JIRA merges the changes in {{DecommissionManager}} from the HDFS-7285 
> branch, including changing a few method names to be more generic 
> ({{replicated}} -> {{stored}}), and some cleanups.



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

Reply via email to