[
https://issues.apache.org/jira/browse/HBASE-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282062#comment-13282062
]
Hudson commented on HBASE-6076:
-------------------------------
Integrated in HBase-TRUNK #2918 (See
[https://builds.apache.org/job/HBase-TRUNK/2918/])
HBASE-6076 Improve h.r.global.memstore.upper(lower)Limit description (Alex
Baranau via JD) (Revision 1342079)
Result = FAILURE
jdcryans :
Files :
* /hbase/trunk/src/main/resources/hbase-default.xml
> Improve h.r.global.memstore.upper(lower)Limit description
> ---------------------------------------------------------
>
> Key: HBASE-6076
> URL: https://issues.apache.org/jira/browse/HBASE-6076
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Alex Baranau
> Assignee: Alex Baranau
> Priority: Trivial
> Attachments: HBASE-6076.patch
>
>
> hbase.regionserver.global.memstore.upper(lower)Limit settings documentation
> (hbase-default.xml) may be misleading. It mentions that:
> * flushes are forced *and updates are blocked* when memstore size reaches
> hbase.regionserver.global.memstore.upperLimit. In this case flushes are
> forced and updates are blocked until memstore size is less than
> hbase.regionserver.global.memstore.lowerLimit.
> But it doesn't mention this:
> * flushes are forced when memstore size hits
> hbase.regionserver.global.memstore.lowerLimit
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
