[
https://issues.apache.org/jira/browse/HBASE-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214075#comment-13214075
]
Phabricator commented on HBASE-5074:
------------------------------------
stack has commented on the revision "[jira] [HBASE-5074] Support checksums in
HBase block cache".
INLINE COMMENTS
src/main/java/org/apache/hadoop/hbase/fs/HFileSystem.java:115 Please ignore
my previous comment on renaming these methods. On reread, I think they are
plenty clear enough as they are.
src/main/java/org/apache/hadoop/hbase/fs/HFileSystem.java:120 Nit: Change
this to be an @return javadoc so its clear we are returning current state of
this flag?
src/main/java/org/apache/hadoop/hbase/fs/HFileSystem.java:164 Does mean that
this feature is on by default? Should we read configuration to figure whether
its on or not?
src/main/java/org/apache/hadoop/hbase/io/hfile/ChecksumUtil.java:73 Is this
threadsafe? This looks like a shared object?
REVISION DETAIL
https://reviews.facebook.net/D1521
> 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
> Attachments: D1521.1.patch, D1521.1.patch, D1521.2.patch,
> D1521.2.patch, D1521.3.patch, D1521.3.patch, D1521.4.patch, D1521.4.patch,
> D1521.5.patch, D1521.5.patch, D1521.6.patch, D1521.6.patch, D1521.7.patch,
> D1521.7.patch, D1521.8.patch, D1521.8.patch
>
>
> 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
