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

Guanglei Xia commented on HBASE-29158:
--------------------------------------

[~ndimiduk] Yes!I think my issue is similar to HBASE-28065, but the scenarios 
we encountered are different. I have made some fixes based on the scenarios we 
encountered to solve our company's online case

> Unknown checksum type code exception occurred while reading HFileBlock
> ----------------------------------------------------------------------
>
>                 Key: HBASE-29158
>                 URL: https://issues.apache.org/jira/browse/HBASE-29158
>             Project: HBase
>          Issue Type: Bug
>          Components: HFile
>    Affects Versions: 2.2.6, 2.6.2
>            Reporter: Guanglei Xia
>            Priority: Major
>              Labels: pull-request-available
>
> In our HBase cluster, we encountered frequent checksum type error messages. 
> After reviewing the relevant Jira, we found that HBASE-28605 had previously 
> discussed the issue of HBase checksum. Currently, HBase checksum does not 
> check the hfile header cache, which can cause some problems when HFile is 
> corrupted. This patch(HBASE-28605) also fixes several cases of corrupt HFile. 
> However, HBASE-28605 cannot solve the problem of checksum type error when the 
> HFile header is corrupted. We propose a new patch to fix the issue of 
> checksum type error. We will check the checksum type value of the hfile 
> header before the checksum. If this is incorrect, it means that the hfile 
> header is corrupted and cannot be used anymore. Finally, this patch was 
> applied in our HBase cluster and the bug has been resolved in our cluster.
> We will provide feedback on this patch to the community and display the error 
> stack in the comments, hoping to receive some guidance......



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to