hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-11550) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
Date Fri, 15 Aug 2014 22:13:19 GMT

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

Andrew Purtell edited comment on HBASE-11550 at 8/15/14 10:11 PM:
------------------------------------------------------------------

bq. I don't think it fair to the new contributor to have their contributions get caught up
in the project politicking.

Hmm, I'm sure there is universal agreement on that point but maybe not agreement that the
only thing happening here on this issue is political in nature. There is a certain amount
of churn on our JIRA caused by filing of (nearly) content-free issues, or considerations of
trivial import. Some are more responsible for that churn than others. Some are more annoyed
by that churn than others. A report filtering for issues closed as Invalid or Cannot Reproduce
will provide indication of both. It is a problem occasionally worth complaint. When it happens
it is indeed bad example, and valid to discuss if the JIRA is helpful or just a distraction.
Disagreement on that point is fine, not politics.


was (Author: apurtell):
bq. I don't think it fair to the new contributor to have their contributions get caught up
in the project politicking.

Hmm, I'm sure there is universal agreement on that point but maybe not agreement that the
only thing happening here on this issue is political in nature. There is a certain amount
of churn on our JIRA caused by filing of content-free issues. Some are more responsible for
that churn than others. Some are more annoyed by that churn than others. A report filtering
for issues closed as Invalid or Cannot Reproduce will provide indication of both. It is a
problem occasionally worth complaint. When it happens it is indeed bad example. 

> 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