[
https://issues.apache.org/jira/browse/HBASE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878198#comment-13878198
]
Anoop Sam John commented on HBASE-10392:
----------------------------------------
Thanks for finding out this Nick! Sorry I missed
In other places where the new config is added, giving BC for the old config
also. So if old config alone is present then also this check should work
correctly right? We can handle that way?
> Correct references to hbase.regionserver.global.memstore.upperLimit
> -------------------------------------------------------------------
>
> Key: HBASE-10392
> URL: https://issues.apache.org/jira/browse/HBASE-10392
> Project: HBase
> Issue Type: Bug
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.99.0
>
> Attachments: HBASE-10392.0.patch
>
>
> As part of the awesome new HBASE-5349, a couple references to
> {{hbase.regionserver.global.memstore.upperLimit}} was missed. Clean those up
> to use the new {{hbase.regionserver.global.memstore.size}} instead.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
