[
https://issues.apache.org/jira/browse/HBASE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909145#comment-13909145
]
Hudson commented on HBASE-10392:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-1.1 #96 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/96/])
HBASE-10392 Correct references to hbase.regionserver.global.memstore.upperLimit
(ndimiduk: rev 1570721)
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HBaseConfiguration.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java
* /hbase/trunk/src/main/docbkx/ops_mgt.xml
* /hbase/trunk/src/main/docbkx/performance.xml
> 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
> Components: documentation
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.99.0
>
> Attachments: HBASE-10392.0.patch, HBASE-10392.1.patch,
> HBASE-10392.2.patch, HBASE-10392.3.patch, HBASE-10392.4.patch,
> HBASE-10392.5.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)
