hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zach York (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17204) Make Off heap Bucket Cache default ON
Date Mon, 11 Dec 2017 20:44:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286518#comment-16286518

Zach York commented on HBASE-17204:

[~stack] [~anoop.hbase] [~ram_krish]

Sorry I'm late to the party here, but I stumbled across this late.
So if I'm reading this correctly, there will by default be no L1 in memory cache if you specify
bucketcache? This will be a problem for our distribution as we still rely on quick lookup
of the L1 cache (in memory) for indexes, bloom filters, etc, but rely on the file based IO
engine for caching data blocks. This could be a blocker for us moving to HBase 2.0.

However, I don't generally disagree with the approach. Perhaps HBASE-18300 should be higher
priority now to allow users to still use off-head and file based BucketCaches concurrently.

> Make Off heap Bucket Cache default ON
> -------------------------------------
>                 Key: HBASE-17204
>                 URL: https://issues.apache.org/jira/browse/HBASE-17204
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>            Priority: Blocker
>             Fix For: 2.0.0-beta-1
> L2 cache can be used for data blocks.  By default it is off now. After HBASE-11425 work,
L2 off heap cache can equally perform with L1 on heap cache. On heavy loaded workload, this
can even out perform L1 cache.  Pls see recently published report by Alibaba.  Also this work
was backported by Rocketfuel and similar perf improvement report from them too.
> Let us turn L2 off heap cache ON. As it is off heap, we can have much larger sized L2
BC.  What should be the default size?

This message was sent by Atlassian JIRA

View raw message