[
https://issues.apache.org/jira/browse/HBASE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878837#comment-13878837
]
Anoop Sam John commented on HBASE-10392:
----------------------------------------
In fact this check is duplicated at 2 places now. But HeapMemoryManager will
get initialized only when the auto tuning is ON.. Thinking whether we can
remove the check at HeapMemoryManager.
> 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)
