[
https://issues.apache.org/jira/browse/HBASE-11910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315942#comment-14315942
]
Hadoop QA commented on HBASE-11910:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12697995/HBASE-11910-v3.patch
against master branch at commit a0f2bc07b27a4119c356b5e2d111cf8e93dfb00e.
ATTACHMENT ID: 12697995
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) 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:
+The link:http://en.wikipedia.org/wiki/CAP_theorem[CAP Theorem] states that
a distributed system can maintain two out of the following three
charateristics:
+- *P*artition tolerance -- the system continues to operate even if some of its
components become unavailable to the others.
+Robert Yokota used an automated testing framework called
link:https://aphyr.com/tags/jepsen[Jepson] to test HBase's partition tolerance
in the face of network partitions, using techniques modeled after Aphyr's
link:https://aphyr.com/posts/281-call-me-maybe-carly-rae-jepsen-and-the-perils-of-network-partitions[Call
Me Maybe] series. The results, available as a
link:http://eng.yammer.com/call-me-maybe-hbase/[blog post] and an
link:http://eng.yammer.com/call-me-maybe-hbase-addendum/[addendum], show that
HBase performs correctly. In the tests, acknowledged writes are accounted for,
and no unacknowledged writes are written.
+Partition-tolerance is not perfect. It is expected that if the client fails at
the right time, the write will be in the WAL, but the RegionServer's
acknowledgment will not reach the client, and then client would assume failure.
{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.mapreduce.TestLoadIncrementalHFiles
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at
org.apache.hadoop.hbase.coprocessor.TestMasterObserver.testRegionTransitionOperations(TestMasterObserver.java:1604)
at
org.apache.hadoop.hbase.namespace.TestNamespaceAuditor.testRegionMerge(TestNamespaceAuditor.java:308)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/12777//console
This message is automatically generated.
> Document Premptive Call Me Maybe HBase findings in the online manual
> --------------------------------------------------------------------
>
> Key: HBASE-11910
> URL: https://issues.apache.org/jira/browse/HBASE-11910
> Project: HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Assignee: Misty Stanley-Jones
> Labels: documentation
> Fix For: 2.0.0
>
> Attachments: HBASE-11910-v1.patch, HBASE-11910-v2.patch,
> HBASE-11910-v3.patch, HBASE-11910.patch
>
>
> Document the Premptive Call Me Maybe HBase findings in the online manual.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
