[
https://issues.apache.org/jira/browse/HBASE-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168733#comment-15168733
]
Liu Shaohui commented on HBASE-15338:
-------------------------------------
[~anoop.hbase]
{quote}
Why we need this new config? Why can not we rely on HCD setting?
{quote}
I think it's better to have a global switch.
{quote}
This may be the issue you are saying? This is called from getMetaBlock(). As
per the comment, when we read meta blocks, we must cache it. As we do not pass
any type we seems may not do that.. That is a bug IMO.. So we better correct
that bug (Any other?) and test ur case with HCD setting?
And ya as per Jingcheng suggestion, we need consider META block category as
well?
{quote}
Thanks for pointing out. I will update patch according Jingcheng's suggestion
and add more tests.
> Add a option to disable the data block cache for testing the performance of
> underlying file system
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-15338
> URL: https://issues.apache.org/jira/browse/HBASE-15338
> Project: HBase
> Issue Type: Improvement
> Components: integration tests
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15338-trunk-v1.diff, HBASE-15338-trunk-v2.diff,
> HBASE-15338-trunk-v3.diff
>
>
> When testing and comparing the performance of different file systems(HDFS,
> Azure blob storage, AWS S3 and so on) for HBase, it's better to avoid the
> affect of the HBase BlockCache and get the actually random read latency when
> data block is read from underlying file system. (Usually, the index block and
> meta block should be cached in memory in the testing).
> So we add a option in CacheConfig to disable the data block cache.
> Suggestions are welcomed~ Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
