[ 
https://issues.apache.org/jira/browse/HADOOP-19180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875024#comment-17875024
 ] 

ASF GitHub Bot commented on HADOOP-19180:
-----------------------------------------

zhengchenyu commented on PR #6813:
URL: https://github.com/apache/hadoop/pull/6813#issuecomment-2297822194

    @zhangshuyan0  @Hexiaoqiao @slfan1989 @haiyang1987 @ZanderXu 
   Thanks for you review. Even though the pr is merged, the failed test still 
exists. And I have verified through the [pr test](#6972) that the failed unit 
test is not caused by this PR. When there are changes to the hadoop-common 
native code, docker ci "precommit-run CentOS 7" will be triggered, then the 
fail unit test was reproduced. 
   
   > Note: If there are no changes to the hadoop-common native code, docker ci 
"precommit-run CentOS 7" will be ignored. The failed unit test will not be 
reproduced.
   
   It is strange! I found that only "precommit-run CentOS 7" will reproduce the 
failures of TestServiceInterruptHandling:: testRegisterAndRaise. I can not 
reproduce this in my environment, even though my environment have been started 
by start-build-env.sh. I will try to fix it in another pr.




> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to