[
https://issues.apache.org/jira/browse/HBASE-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460772#comment-13460772
]
stack commented on HBASE-6798:
------------------------------
[~liulei.cn] Please open a new issue. We could do something like an add
setSkipChecksum per file to hdfs or we could write checksums into WAL if this
skip checksum facility is enabled (or have the WAL system use an fs w/
checksuming on). I was looking through the HBASE-5074 to figure how we fall
back on the HDFS checksum but had to give up for the moment. Lets carry the
discussion on in a new issue rather than on the tail of this closed one.
Thanks for finding this.
> HDFS always read checksum form meta file
> ----------------------------------------
>
> Key: HBASE-6798
> URL: https://issues.apache.org/jira/browse/HBASE-6798
> Project: HBase
> Issue Type: Bug
> Components: Performance
> Affects Versions: 0.94.0, 0.94.1
> Reporter: LiuLei
> Priority: Blocker
> Attachments: 6798.txt
>
>
> I use hbase0.941 and hadoop-0.20.2-cdh3u5 version.
> The HBase support checksums in HBase block cache in HBASE-5074 jira.
> The HBase support checksums for decrease the iops of HDFS, so that HDFS
> dont't need to read the checksum from meta file of block file.
> But in hadoop-0.20.2-cdh3u5 version, BlockSender still read the metadata file
> even if the
> hbase.regionserver.checksum.verify property is ture.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
