[
https://issues.apache.org/jira/browse/HBASE-26780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783914#comment-17783914
]
Nick Dimiduk commented on HBASE-26780:
--------------------------------------
For us, HBASE-28065 happened when the server's drives were failing. Server load
could be light or it could be heavy. When load was heavy, it would happen more
often. The fix on 28065 plugs several holes in the {{useHBaseChecksum=true}}
code path so that it will fall back to HDFS checksum and mark affected HDFS
block as needing to be re-replicated. I'll be curious if you can reproduce the
issue after you've upgraded to 2.4.18/2.5.6/2.6.0. Pay closer attention to your
hosts that have older drives.
> 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)
