[
https://issues.apache.org/jira/browse/HBASE-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173006#comment-13173006
]
dhruba borthakur commented on HBASE-5074:
-----------------------------------------
Todd: you are right. that would make life easy.
I am proposing that HBase disk format V3 have a 4 byte checksum for every hbase
block. This will not require checksums and data to be stored inline in HDFS
while at the same-time allow hbase to do additional iops. One minor
disadvantage of this approach is that checksums would be computed twice, once
by the hbase regionserver and once by the hdfs client. How bad is this cpu
overhead?
BTW, I got this idea while chatting with Nicolas Spiegelberg. Credits to him
for this elegant idea.
> support checksums in HBase block cache
> --------------------------------------
>
> Key: HBASE-5074
> URL: https://issues.apache.org/jira/browse/HBASE-5074
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> The current implementation of HDFS stores the data in one block file and the
> metadata(checksum) in another block file. This means that every read into the
> HBase block cache actually consumes two disk iops, one to the datafile and
> one to the checksum file. This is a major problem for scaling HBase, because
> HBase is usually bottlenecked on the number of random disk iops that the
> storage-hardware offers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
