hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Esteban Gutierrez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13729) Old hbase.regionserver.global.memstore.upperLimit is ignored if present
Date Wed, 20 May 2015 22:35:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Esteban Gutierrez updated HBASE-13729:
--------------------------------------
    Status: Open  (was: Patch Available)

> Old hbase.regionserver.global.memstore.upperLimit is ignored if present
> -----------------------------------------------------------------------
>
>                 Key: HBASE-13729
>                 URL: https://issues.apache.org/jira/browse/HBASE-13729
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 1.1.0, 1.0.1, 2.0.0
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Critical
>         Attachments: 0001-HBASE-13729-Old-hbase.regionserver.global.memstore.u.patch
>
>
> If hbase.regionserver.global.memstore.upperLimit is present we should use it instead
of hbase.regionserver.global.memstore.size the current implementation of HeapMemorySizeUtil.getGlobalMemStorePercent()
asumes that if hbase.regionserver.global.memstore.size is not defined thenit should use the
old configuration, however it should be the other way around.
> This has a large impact specially if doing a rolling upgrade of a cluster when the memstore
upper limit has been changed from the default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message