[
https://issues.apache.org/jira/browse/HBASE-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088713#comment-14088713
]
Hadoop QA commented on HBASE-11629:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12660258/HBASE-11629.patch
against trunk revision .
ATTACHMENT ID: 12660258
{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: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 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{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.TestRegionRebalancing
{color:red}-1 core zombie tests{color}. There are 3 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10330//console
This message is automatically generated.
> Operational concerns for Replication should call out ZooKeeper
> --------------------------------------------------------------
>
> Key: HBASE-11629
> URL: https://issues.apache.org/jira/browse/HBASE-11629
> Project: HBase
> Issue Type: Bug
> Components: documentation, Replication
> Reporter: Sean Busbey
> Assignee: Misty Stanley-Jones
> Attachments: HBASE-11629.patch
>
>
> Our [design invariants state that ZooKeeper data is safe to
> delete|http://hbase.apache.org/book/developing.html#design.invariants.zk.data].
> However, [replication only stores its data in
> zookeeper|http://hbase.apache.org/replication.html#Replication_Zookeeper_State].
>
> This can lead to operators accidentally disabling their replication set up
> while attempting to recover from an unrelated issue by clearing the zk state.
> We should update the [operational concerns section on
> replication|http://hbase.apache.org/book/cluster_replication.html] to call
> out that the /hbase/replication tree should not be deleted. We should
> probably also add a warning to the set up steps.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
