hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9855) evictBlocksByHfileName improvement for bucket cache
Date Sun, 03 Nov 2013 05:36:19 GMT

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

stack updated HBASE-9855:
-------------------------

       Resolution: Fixed
    Fix Version/s: 0.96.1
                   0.98.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed this improvement on 0.96 (because bucket cache an experimental feature) and on trunk.
 Thanks for the forward port [~xieliang007] (and to the reviewers)



> evictBlocksByHfileName improvement for bucket cache
> ---------------------------------------------------
>
>                 Key: HBASE-9855
>                 URL: https://issues.apache.org/jira/browse/HBASE-9855
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.98.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: HBase-9855-v4.txt
>
>
> In deed, it comes from fb's l2 cache by [~avf]'s nice work,  i just did a simple backport
here. It could improve a linear-time search through the whole cache map into a log-access-time
map search.
> I did a small bench, showed it brings a bit gc overhead, but considering the evict on
close triggered by frequent compaction activity, seems reasonable?
> and i thought bring a "evictOnClose" config  into BucketCache ctor and only put/remove
the new index map while evictOnClose is true, seems this value could be set by each family
schema, but BucketCache is a global instance not per each family, so just ignore it rightnow...



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message