You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "yuzhang (Jira)" <ji...@apache.org> on 2023/11/07 06:13:00 UTC

[jira] [Commented] (HBASE-26780) HFileBlock.verifyOnDiskSizeMatchesHeader throw IOException: Passed in onDiskSizeWithHeader= A != B

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

yuzhang commented on HBASE-26780:
---------------------------------

thanks [~cribbee] ,[~xytss123] ,[~ndimiduk] . Sorry for noticing the responses so late.

Actually, since we split our hbase cluster, this Exception has rarely happen. We split the hbase cluster for the engine room is full and we think our hbase cluster is too large. 

Before split, there is 328 rs, 552,383 regions, 1,700 average load, 16PB data. We move the hot data to a new cluster which hbase verision is 2.4.5 

Now, old cluster is 1,900 average load, new cluster is 2,700. Seems that this problem not caused by high load. 

> HFileBlock.verifyOnDiskSizeMatchesHeader throw IOException: Passed in onDiskSizeWithHeader= A != B
> --------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-26780
>                 URL: https://issues.apache.org/jira/browse/HBASE-26780
>             Project: HBase
>          Issue Type: Bug
>          Components: BlockCache
>    Affects Versions: 2.2.2
>            Reporter: yuzhang
>            Priority: Major
>         Attachments: IOException.png
>
>
> When I scan a region, HBase throw IOException: Passed in onDiskSizeWithHeader= A != B
> The HFile mentioned Error message can be access normally.
> it recover by command – move region. I guess that onDiskSizeWithHeader of HFileBlock has been changed. And RS get the correct BlockHeader Info after region reopened.
>  



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