[
https://issues.apache.org/jira/browse/HBASE-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015171#comment-14015171
]
Hadoop QA commented on HBASE-6701:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12647848/HBASE-6701-rebased.patch
against trunk revision .
ATTACHMENT ID: 12647848
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ <para>The balancer is a periodic operation which is run on the
master to redistribute regions on the cluster. It is configured via
+ <para>See <xref linkend="master.processes.loadbalancer" /> for more
information on the LoadBalancer.
+ <para>Do not turn off block cache (You'd do it by setting
<varname>hbase.block.cache.size</varname> to zero).
+ Currently we do not do well if you do this because the regionserver
will spend all its time loading hfile
+ indices over and over again. If your working set it such that
block cache does you no good, at least
+ size the block cache such that hfile indices will stay up in the
cache (you can get a rough idea
+ on the size you need by surveying regionserver UIs; you'll see
index block size accounted near the
+ <title><link
xlink:href="http://en.wikipedia.org/wiki/Nagle's_algorithm">Nagle's</link> or
the small package problem</title>
+ <link
xlink:href="http://search-hadoop.com/m/pduLg2fydtE/Inconsistent+scan+performance+with+caching+set+&subj=Re+Inconsistent+scan+performance+with+caching+set+to+1";>Inconsistent
scan performance with caching set to 1</link>
+ see the graphs on the tail of <link
xlink:href="https://issues.apache.org/jira/browse/HBASE-7008";>HBASE-7008 Set
scanner caching to a better default</link>
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestMultiParallel
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9660//console
This message is automatically generated.
> Revisit thrust of paragraph on splitting
> ----------------------------------------
>
> Key: HBASE-6701
> URL: https://issues.apache.org/jira/browse/HBASE-6701
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: stack
> Assignee: Misty Stanley-Jones
> Attachments: HBASE-6701-rebased.patch, HBASE-6701.patch
>
>
> See the thread 'md5 hash key and splits' for the confusion our paragraph on
> splitting seems to bring on (as well as good input on when manual splitting
> might be favored). The user is under the impression that he needs to
> manually split though his keys have md5 salt. The paragraph needs to make
> sure it does not bring on such confusion as it would seem to in this case.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
