[
https://issues.apache.org/jira/browse/HBASE-13729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575509#comment-14575509
]
Enis Soztutar commented on HBASE-13729:
---------------------------------------
bq. Pushed to branch-1.0+ (FYI Enis Soztutar and Nick Dimiduk).
Thanks for the ping. +1 for the patch. It is important for rolling upgrades.
> Old hbase.regionserver.global.memstore.upperLimit and lowerLimit properties
> are ignored if present
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-13729
> URL: https://issues.apache.org/jira/browse/HBASE-13729
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 2.0.0, 1.0.1, 1.1.0
> Reporter: Esteban Gutierrez
> Assignee: Esteban Gutierrez
> Priority: Critical
> Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.1
>
> Attachments:
> 0001-HBASE-13729-Old-hbase.regionserver.global.memstore.u.patch,
> HBASE-13729.2.patch, HBASE-13729.3.patch, HBASE-13729.4.patch
>
>
> If hbase.regionserver.global.memstore.upperLimit or lowerLimit are present we
> should use them instead of hbase.regionserver.global.memstore.size or
> hbase.regionserver.global.memstore.size.lower.limit respectively. The current
> implementation of HeapMemorySizeUtil.getGlobalMemStorePercent() and
> getGlobalMemStoreLowerMark() asumes that if the new properties are not
> defined then we should use the old configurations, however the new properties
> are defined in hbase-default.xml which makes the old configuration names
> useless and this has a direct impact when doing a rolling upgrade and
> hbase-site.xml hasn't been changed to handle the new property names
> exclusively.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
