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-11550) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
Date Fri, 15 Aug 2014 04:38:19 GMT

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

stack updated HBASE-11550:
--------------------------

    Priority: Trivial  (was: Major)

Marking trivial again. Thought we were going to get some questions answered in this JIRA ('wastage')
but it turns out not. Fix the priority if you think I have it wrong.

Filing an issue to add a test for a patch already committed is elision complicating accounting,
wasting a JIRA, and teaching a new committer dodgy practice.

> 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
>            Priority: Trivial
>             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
(v6.2#6252)

Mime
View raw message