[
https://issues.apache.org/jira/browse/HDFS-17535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865983#comment-17865983
]
Hongbing Wang commented on HDFS-17535:
--------------------------------------
[~ruilaing] We had similar problems without pr HDFS-15240 in previous years
and there seemed to be no convenient tool to fix them. We also use structured
data (orc/parquet) features for verifying data, and the overall idea is similar
to yours.
For RS-6-3, if more than 3 blocks are broken unfortunately, it will be not
recoverable.
> I have confirmed the EC corrupt file, can this corrupt file be restored?
> ------------------------------------------------------------------------
>
> Key: HDFS-17535
> URL: https://issues.apache.org/jira/browse/HDFS-17535
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ec, hdfs
> Affects Versions: 3.1.0
> Reporter: ruiliang
> Priority: Blocker
>
> I learned that EC does have a major bug with file corrupt
> https://issues.apache.org/jira/browse/HDFS-15759
> 1：I have confirmed the EC corrupt file, can this corrupt file be restored?
> Have important data that is causing us production data loss issues? Is
> there a way to recover
> Checking EC block group: blk_-9223372036361352768
> Status: ERROR, message: EC compute result not match.:ip is 10.12.66.116 block
> is : -9223372036361352765
> 2：[https://github.com/apache/orc/issues/1939] I was wondering if cherry
> picked your current code (GitHub pull request #2869), Can I skip patches
> related to HDFS-14768,HDFS-15186, and HDFS-15240?
> hdfs version 3.1.0
> thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
