[
https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162260#comment-14162260
]
Andrey Stepachev commented on HBASE-12016:
------------------------------------------
[~apurtell], can you look at code
org/apache/hadoop/hbase/security/access/AccessController.java:2177, I think we
need to remove checks for isTableModifiable here. Only validate that table
exists.
[~ted_yu] thank you for reviewing. block size was got from previous code just
by extracting constant, so I didn't thought much about why that value was
selected.
Regarding setInfoFamilyCaching, this method is static and applied to Meta only.
So it is good to be explicit here, so I'd prefer to state in method name that
this method is for meta only.
> Reduce number of versions in Meta table. Make it configurable
> -------------------------------------------------------------
>
> Key: HBASE-12016
> URL: https://issues.apache.org/jira/browse/HBASE-12016
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Andrey Stepachev
> Assignee: Andrey Stepachev
> Priority: Minor
> Fix For: 2.0.0, 0.98.8, 0.99.1
>
> Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch,
> HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch
>
>
> Currently meta keeps up to 10 versions of each KV.
> For big metas it leads to substantial memory overhead and scan slowdowns.
> (see https://issues.apache.org/jira/browse/HBASE-11165 )
> Need to keep reasonable number of versions (suggested value is 3).
> Number of versions configurable via parameter: hbase.meta.versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
