hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13729) Old hbase.regionserver.global.memstore.upperLimit and lowerLimit properties are ignored if present
Date Fri, 05 Jun 2015 22:21:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575338#comment-14575338
] 

Hudson commented on HBASE-13729:
--------------------------------

SUCCESS: Integrated in HBase-1.1 #525 (See [https://builds.apache.org/job/HBase-1.1/525/])
HBASE-13729 Old hbase.regionserver.global.memstore.upperLimit and lowerLimit properties are
ignored if present (Esteban Guitierrez) (stack: rev 8fd6c0bae8abb95643deafb25488386dba3a140c)
* hbase-common/src/main/resources/hbase-default.xml


> 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)

Mime
View raw message