[
https://issues.apache.org/jira/browse/HDFS-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601155#comment-14601155
]
Walter Su commented on HDFS-8652:
---------------------------------
We know it keep tracks of replica(b.corrupted), instead of
storedBlock(b.stored), from the class name {{CorruptedReplicasMap}}.
But a (storedBlock, node) pair can represents a replica, right?
So for striped block, we can save (storedBlock, node) pair to represents a
internal block, which corrupted.
bq. In BlockToMarkCorrupt, b.corrupted and b.stored may have different
generation stamp.
The question is, do we need the information about the corrupted replica?
I don't think so. We already saved {{Reason}} why it's corrupted. After all,
(blockid, node, reason) is all we need to know about a corrupted replica.
> 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
> Attachments: HDFS-8652.000.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)
