[
https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139799#comment-14139799
]
stack commented on HBASE-12016:
-------------------------------
Undoing the hardcoding of meta is the right way to go. I see this patch as fine
for now but imagine we could be in for some interesting times when meta
actually changes an attribute.... Lets see how it goes..
Patch looks good to me except for the nit that meta is defined in
FSTableDescriptor rather than say in TableDescriptor. If we have another
registry implementation, it would have to copy the FSTD definition for meta?
> 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.7, 0.99.1
>
> Attachments: 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)
