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

Hudson commented on HBASE-29158:
--------------------------------

Results for branch branch-2
        [build #1250 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1250/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test for HBase 2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}


> 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
>            Assignee: Guanglei Xia
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0-beta-2, 2.6.3, 2.5.12
>
>
> 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