[
https://issues.apache.org/jira/browse/HDFS-16776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868912#comment-17868912
]
ASF GitHub Bot commented on HDFS-16776:
---------------------------------------
LoseYSelf commented on PR #6964:
URL: https://github.com/apache/hadoop/pull/6964#issuecomment-2252445648
i have an idea,we can limit the BlockPlacementPolicyDefault to choose ec
target one by one,so it will not break dn checkArgument, , instead of choose
all target storageType
> Erasure Coding: The length of targets should be checked when DN gets a
> reconstruction task
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-16776
> URL: https://issues.apache.org/jira/browse/HDFS-16776
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: erasure-coding
> Affects Versions: 3.4.0, 3.3.5
> Reporter: Ruinan Gu
> Assignee: Ruinan Gu
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.5, 3.2.5
>
>
> The length of targets should be checked when DN gets a EC reconstruction
> task.For some reason (HDFS-14768, HDFS-16739) , the length of targets will be
> larger than additionalReplRequired which causes some elements in targets get
> the default value 0. It may trigger the bug which leads to the data
> corrupttion just like HDFS-14768.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
