[
https://issues.apache.org/jira/browse/HBASE-26780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762626#comment-17762626
]
Nick Dimiduk commented on HBASE-26780:
--------------------------------------
[~cribbee] Thanks for the stack trace. I think that my patch on HBASE-28065
will indeed improve the handling of this example you posted. I think it will
help because it (1) re-orders the sequence of actions to perform checksum
validation before accessing the hfileblock header value and (2) it will
propagate such a failure back up to be retried with HDFS checksum validation
enabled. Such a file may still be broken, which my patch cannot fix, but at
least it will be sure that the data was read with checksum enabled.
> 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)
