Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 27 May 2014 01:59:01 +0000 (UTC)
From: "Misty Stanley-Jones (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12655279.1372404241538.19875.1401155941994@arcas>
In-Reply-To: <JIRA.12655279.1372404241538@arcas>
References: <JIRA.12655279.1372404241538@arcas>
Subject: [jira] [Commented] (HBASE-8817) Enhance The Apache HBase Reference
 Guide
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Misty Stanley-Jones commented on HBASE-8817:
--------------------------------------------

Added hbase.regionserver.global.memstore.upperLimit to hbase-default.xml. hbase.hregion.memstore.flush.size was already there.

Added the MemStore Flush section directly below the modified MemStore section.

Added the info about Scans directly after the new MemStore Flush section, though this didn't seem like the best place. I couldn't believe there was not a place in the Ref Guide that specifically talked about doing scans?? Am I missing it?


> Enhance The Apache HBase Reference Guide
> ----------------------------------------
>
>                 Key: HBASE-8817
>                 URL: https://issues.apache.org/jira/browse/HBASE-8817
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Thomas Pan
>            Assignee: Misty Stanley-Jones
>            Priority: Critical
>         Attachments: HBASE-8817.patch
>
>
> I am reading the guide here: http://hbase.apache.org/book.html#regions.arch
> I have noticed the following:
> - There is lack of coverage on scan. Note that Lars has a very good presentation from last year's HBaseCon: http://www.slideshare.net/cloudera/3-learning-h-base-internals-lars-hofhansl-salesforce-final
> - Under section 9.7.6.1, there is no mentioning of flush per region if a memstore reached the size threshold (and a possible flush of all memstores if over all memory usage of all the memstores reached memstore.upperlimit). Note that people need to combine the information provided in section 9 with section 2.3.1.1 to fully understand the situation.
> - Compaction tuning strategies. Both Nicolas from Facebook and Sergey from Hortonworks have presented various compaction algorithms. Sometime, once all the necessary code is in master, we need to have the coverage.
> Let me know how I can help on the matter.


--
This message was sent by Atlassian JIRA
(v6.2#6252)