Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 22 Sep 2012 08:34:08 +1100 (NCT)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <663165451.109597.1348263248585.JavaMail.jiratomcat@arcas>
In-Reply-To: <507470185.33435.1346779207879.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6714)
 TestMultiSlaveReplication#testMultiSlaveReplication may fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-6714:
-------------------------------

Integrated in HBase-0.94-security #54 (See [https://builds.apache.org/job/HBase-0.94-security/54/])
    HBASE-6714 TestMultiSlaveReplication#testMultiSlaveReplication may fail (Revision 1388621)

     Result = ABORTED
stack : 
Files : 
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/replication/TestMultiSlaveReplication.java

                
> TestMultiSlaveReplication#testMultiSlaveReplication may fail
> ------------------------------------------------------------
>
>                 Key: HBASE-6714
>                 URL: https://issues.apache.org/jira/browse/HBASE-6714
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication, test
>    Affects Versions: 0.92.0, 0.94.0
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>            Priority: Minor
>             Fix For: 0.94.2, 0.96.0
>
>         Attachments: HBase-6714-v1.patch
>
>
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.failNotEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:128)
> at org.junit.Assert.assertEquals(Assert.java:472)
> at org.junit.Assert.assertEquals(Assert.java:456)
> at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203)
> at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> TestMultiSlaveReplication->testMultiSlaveReplication failed in our local build citing that "row" was not replicated to second peer. This is because after inserting "row", log is rolled and we look for "row2" in both the clusters and then we check for existence of "row" in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row "row2" is not present in the second cluster from the very beginning. So, the "row2" existence check succeeds and control move on to find "row" in both clusters where it fails for the second cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira