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

Hadoop QA commented on HBASE-10156:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12622266/10156v5.txt
  against trunk revision .
  ATTACHMENT ID: 12622266

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 12 new 
or modified tests.

    {color:green}+1 hadoop1.0{color}.  The patch compiles against the hadoop 
1.0 profile.

    {color:green}+1 hadoop1.1{color}.  The patch compiles against the hadoop 
1.1 profile.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 2 
warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {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:
    +    System.err.println("         For example: FSHLog --dump 
hdfs://example.com:9000/hbase/.logs/MACHINE/LOGFILE");
+    System.err.println("         For example: FSHLog --split 
hdfs://example.com:9000/hbase/.logs/DIR");
+     * @return the WALTrailer of the current HLog. It may be null in case of 
legacy or corrupt WAL files.
+    // TODO: What we need a trailer on WAL for?  It won't be present on the 
last WAL most of the time.  What then?
+   * Utility class that lets us keep track of the edit and it's associated 
key. Only used when splitting logs.
+   * Used by tests only and in rare cases where we need a log just temporarily 
while bootstrapping a region or
+   * Same as {@link #appendNoSync(HRegionInfo, TableName, WALEdit, List, long, 
HTableDescriptor, AtomicLong, boolean, long, long)}
+   * log-sequence-id. The WAL is not flushed/sync'd after this transaction 
completes.  Call {@link #sync()} to
+   * @param sequenceId A reference to the atomic long the <code>info</code> 
region is using as source of its
+   * incrementing edits sequence id.  Inside in this call we will increment it 
and attach the sequence to the edit

    {color:red}-1 site{color}.  The patch appears to cause mvn site goal to 
fail.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.master.TestRollingRestart
                  org.apache.hadoop.hbase.mapreduce.TestHLogRecordReader

     {color:red}-1 core zombie tests{color}.  There are 5 zombie test(s):       
at 
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnDatanodeDeath(TestLogRolling.java:368)
        at 
org.apache.hadoop.hbase.regionserver.TestParallelPut.testParallelPuts(TestParallelPut.java:139)

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/8380//console

This message is automatically generated.

> Fix up the HBASE-8755 slowdown when low contention
> --------------------------------------------------
>
>                 Key: HBASE-10156
>                 URL: https://issues.apache.org/jira/browse/HBASE-10156
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>            Reporter: stack
>            Assignee: stack
>         Attachments: 10156.txt, 10156v2.txt, 10156v3.txt, 10156v4.txt, 
> 10156v5.txt, Disrupting.java
>
>
> HBASE-8755 slows our writes when only a few clients.  Fix.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to