[
https://issues.apache.org/jira/browse/HBASE-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009978#comment-14009978
]
Hudson commented on HBASE-8817:
-------------------------------
FAILURE: Integrated in HBase-TRUNK #5144 (See
[https://builds.apache.org/job/HBase-TRUNK/5144/])
HBASE-8817 Enhance The Apache HBase Reference Guide (Misty Stanley-Jones)
(stack: rev bfbc6d48cd783ce0ea9a43fded0999839fc5d6c5)
* hbase-common/src/main/resources/hbase-default.xml
* src/main/docbkx/book.xml
> 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
> Fix For: 0.99.0
>
> Attachments: HBASE-8817.patch, HBASE-8817v2.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)
