hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
Date Fri, 21 Sep 2012 19:03:08 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-6714:

       Resolution: Fixed
    Fix Version/s: 0.96.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to 0.94 and to trunk.  Thanks for the patch Himanshu.
> 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

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

View raw message