hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11550) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
Date Thu, 14 Aug 2014 16:48:12 GMT

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

Nick Dimiduk commented on HBASE-11550:

I committed v4 of this patch because it ensures the placement semantics are identical for
the default setting and user-provided value, something I inadvertently missed in HBASE-10641.

Yes, I think a test would be good. Wastage will depend on the size of buckets, the placement
strategy used, and the sequence of block sizes inserted. The difficulty with a test is that
memory allocation strategies are not black-and-white. It could well be that there's a better
strategy for most of our users than the current greedy approach. I guess there's now HBASE-11743
that will look at this.

> Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
> ----------------------------------------------------------
>                 Key: HBASE-11550
>                 URL: https://issues.apache.org/jira/browse/HBASE-11550
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.99.0, 0.98.4, 0.98.5
>            Reporter: Ted Yu
>            Assignee: Gustavo Anatoly
>             Fix For: 0.99.0, 2.0.0, 0.98.6
>         Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550-v3.patch,
HBASE-11550-v4-0.98.patch, HBASE-11550-v4.patch, HBASE-11550.patch
> User can pass bucket sizes through "hbase.bucketcache.bucket.sizes" config entry.
> The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2().

This message was sent by Atlassian JIRA

View raw message