hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19357) Bucket cache no longer L2 for LRU cache
Date Thu, 07 Dec 2017 09:41:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anoop Sam John updated HBASE-19357:
-----------------------------------
      Resolution: Fixed
    Hadoop Flags: Incompatible change,Reviewed
    Release Note: 
Removed cacheDataInL1 option for HCD
BucketCache is no longer the L2 for LRU on heap cache. When BC is used, data blocks will be
strictly on BC only where as index/bloom blocks are on LRU L1 cache.
Config 'hbase.bucketcache.combinedcache.enabled' is removed. There is no way set combined
mode = false. Means make BC as victim handler for LRU cache.
          Status: Resolved  (was: Patch Available)

Pushed to branch-2 +//  Thanks for the reviews and discussion.  Started the perf test as discussed
above. Will do followup work as per the test results.

> Bucket cache no longer L2 for LRU cache
> ---------------------------------------
>
>                 Key: HBASE-19357
>                 URL: https://issues.apache.org/jira/browse/HBASE-19357
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19357.patch, HBASE-19357.patch, HBASE-19357_V2.patch, HBASE-19357_V3.patch,
HBASE-19357_V3.patch
>
>
> When Bucket cache is used, by default we dont configure it as an L2 cache alone. The
default setting is combined mode ON where the data blocks to Bucket cache and index/bloom
blocks go to LRU cache. But there is a way to turn this off and make LRU as L1 and Bucket
cache as a victim handler for L1. It will be just L2.   
> After the off heap read path optimization Bucket cache is no longer slower compared to
L1. We have test results on data sizes from 12 GB.  The Alibaba use case was also with 12
GB and they have observed a ~30% QPS improve over the LRU cache.
> This issue is to remove the option for combined mode = false. So when Bucket cache is
in use, data blocks will go to it only and LRU will get only index /meta/bloom blocks.   Bucket
cache will no longer be configured as a victim handler for LRU.
> Note : WHen external cache is in use, there only the L1 L2 thing comes. LRU will be L1
and external cache act as its L2. That make full sense.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message