[
https://issues.apache.org/jira/browse/HDFS-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617017#comment-14617017
]
Jing Zhao commented on HDFS-8652:
---------------------------------
bq. A BlockInfo's genstamp and/or size may mutate.
This is a valid point. Thanks for pointing this out, Daryn. I've reverted the
patch from trunk and branch-2. In the meanwhile, I will revisit HDFS-8619 and
find a new way to track corrupted internal blocks for a striped block group.
> Track BlockInfo instead of Block in CorruptReplicasMap
> ------------------------------------------------------
>
> Key: HDFS-8652
> URL: https://issues.apache.org/jira/browse/HDFS-8652
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Fix For: 2.8.0
>
> Attachments: HDFS-8652.000.patch, HDFS-8652.001.patch,
> HDFS-8652.002.patch
>
>
> Currently {{CorruptReplicasMap}} uses {{Block}} as its key and records the
> list of DataNodes with corrupted replicas. For Erasure Coding since a striped
> block group contains multiple internal blocks with different block ID, we
> should use {{BlockInfo}} as the key.
> HDFS-8619 is the jira to fix this for EC. To ease merging we will use jira to
> first make changes in trunk/branch-2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
