[
https://issues.apache.org/jira/browse/HDFS-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035300#comment-15035300
]
Hudson commented on HDFS-9485:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #656 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/656/])
HDFS-9485. Make BlockManager#removeFromExcessReplicateMap accept (jing9: rev
830eb252aaa4fec7ef2ec38cb66f669e8e1ecaa5)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirWriteFileOp.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> Make BlockManager#removeFromExcessReplicateMap accept BlockInfo instead of
> Block
> --------------------------------------------------------------------------------
>
> Key: HDFS-9485
> URL: https://issues.apache.org/jira/browse/HDFS-9485
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HDFS-9485.000.patch
>
>
> The {{BlockManager#removeFromExcessReplicateMap()}} method accepts a
> {{Block}} which is to remove from {{excessReplicateMap}}. However the
> {{excessReplicateMap}} maps a StorageID to the set of {{BlockInfo}} that are
> "extra" for the DataNode of the StorageID. Deleting a sub-class object from a
> collection provided a base-class object happens to work here.
> Alternatively, we can make the {{removeFromExcessReplicateMap}} accept a
> {{BlockInfo}} object. As the current call stack is passing {{BlockInfo}}
> object mostly, the code change should be safe.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
