[
https://issues.apache.org/jira/browse/HBASE-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482057#comment-14482057
]
Hadoop QA commented on HBASE-13413:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12723403/HBASE-13413.patch
against master branch at commit 8c707499baa2a5472680f98b19356bc1e104bcd8.
ATTACHMENT ID: 12723403
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ * This creates a new ClusterID wrapper that will automatically build
connections and configurations
+ * The main runner loop for the test. It uses the {@link
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList}
+ * This tears down any tables that existed from before and rebuilds the
tables and schemas on the source cluster.
+ * It then sets up replication from the source to the sink cluster by
using the {@link org.apache.hadoop.hbase.client.replication.ReplicationAdmin}
+ for (HRegionLocation rl :
cluster.getConnection().getRegionLocator(tableName).getAllRegionLocations()) {
+ * Run the {@link
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList.Generator} in the
source cluster
+ * Run the {@link
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList.Verify} in the sink
cluster.
+ * If replication is working properly the data written at the source
cluster should be available in the sink cluster
+ addRequiredOptWithArg("s", SOURCE_CLUSTER_OPT, "Cluster ID of the source
cluster (e.g. localhost:2181:/hbase)");
+ addRequiredOptWithArg("r", DEST_CLUSTER_OPT, "Cluster ID of the sink
cluster (e.g. localhost:2182:/hbase)");
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13586//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13586//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13586//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13586//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13586//console
This message is automatically generated.
> Create an integration test for Replication
> ------------------------------------------
>
> Key: HBASE-13413
> URL: https://issues.apache.org/jira/browse/HBASE-13413
> Project: HBase
> Issue Type: Test
> Components: integration tests
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Rajesh Nishtala
> Assignee: Rajesh Nishtala
> Priority: Minor
> Attachments: HBASE-13413.patch
>
>
> We want to have an end-to-end test for replication. it can write data into
> one cluster (with replication setup) and then read data from the other. The
> test should be capable of running for a long time and be reliant even under
> chaos monkey testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)