[
https://issues.apache.org/jira/browse/HBASE-11625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158528#comment-14158528
]
Andrew Purtell edited comment on HBASE-11625 at 10/3/14 9:12 PM:
-----------------------------------------------------------------
bq. The other interesting bit is that the test only starts failing after
0.98.3.
0.98.3 was released June 7. Here are commits touching o.a.h.h.io.hfile in
hbase-server in 0.98 since that date, excluding changes to block cache given
the above description: HBASE-11118, HBASE-11437, HBASE-11586, HBASE-11331,
HBASE-11845, HBASE-12059, HBASE-12076, HBASE-12123. I think we can suspect less
later changes like HBASE-11331 and beyond if this is observable in releases
like 0.98.4.
was (Author: apurtell):
bq. The other interesting bit is that the test only starts failing after
0.98.3.
0.98.3 was released June 7. Here are commits touching o.a.h.h.io.hfile in
hbase-server in 0.98 since that date, excluding changes to LRU given the above
description: HBASE-11118, HBASE-11437, HBASE 11586, HBASE-11331, HBASE-11845,
HBASE-12059, HBASE-12076, HBASE-12123. I think we can suspect less later
changes like HBASE-11331 and beyond if this is observable in releases like
0.98.4.
> Reading datablock throws "Invalid HFile block magic" and can not switch to
> hdfs checksum
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-11625
> URL: https://issues.apache.org/jira/browse/HBASE-11625
> Project: HBase
> Issue Type: Bug
> Components: HFile
> Affects Versions: 0.94.21, 0.98.4, 0.98.5
> Reporter: qian wang
> Attachments: 2711de1fdf73419d9f8afc6a8b86ce64.gz
>
>
> when using hbase checksum,call readBlockDataInternal() in hfileblock.java, it
> could happen file corruption but it only can switch to hdfs checksum
> inputstream till validateBlockChecksum(). If the datablock's header corrupted
> when b = new HFileBlock(),it throws the exception "Invalid HFile block magic"
> and the rpc call fail
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
