You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/06/13 06:47:00 UTC
[jira] [Commented] (HADOOP-19180) EC: Fix calculation errors caused by special index order
[ https://issues.apache.org/jira/browse/HADOOP-19180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854645#comment-17854645 ]
ASF GitHub Bot commented on HADOOP-19180:
-----------------------------------------
zhengchenyu commented on PR #6813:
URL: https://github.com/apache/hadoop/pull/6813#issuecomment-2164660043
@drankye @sodonnel @cmccabe
Do you have time to help review it?
> EC: Fix calculation errors caused by special index order
> --------------------------------------------------------
>
> Key: HADOOP-19180
> URL: https://issues.apache.org/jira/browse/HADOOP-19180
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Chenyu Zheng
> Assignee: Chenyu Zheng
> Priority: Critical
> Labels: pull-request-available
>
> I found that if the erasedIndexes distribution is such that the parity index is in front of the data index, ec will produce wrong results when decoding.
> In fact, HDFS-15186 has described this problem, but does not fundamentally solve it.
> The reason is that the code assumes that erasedIndexes is preceded by the data index and followed by parity index. If there is a parity index placed in front of the data index, a calculation error will occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org