[
https://issues.apache.org/jira/browse/HBASE-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457327#comment-13457327
]
Todd Lipcon commented on HBASE-6798:
------------------------------------
Fixing this for remote reads (ie not short circuit ones) is going to be
somewhat tricky for Hadoop 1.0, because we need to keep protocol compatibility.
Doing it for Hadoop 2 shouldn't be bad, because we have protobufs, but will
still take a bit of careful HDFS surgery. I vaguely remember an existing HDFS
JIRA about this, but now not sure where it went. Anyone remember the number or
should we re-file?
> 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
>
> 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
