[
https://issues.apache.org/jira/browse/HBASE-10189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851999#comment-13851999
]
Demai Ni commented on HBASE-10189:
----------------------------------
(thanks to Ted who detected this).
this is another recent failure:
https://builds.apache.org/job/hbase-0.98/20/testReport/org.apache.hadoop.hbase.replication/TestReplicationSyncUpTool/testSyncUpTool/
(Build #20 (Dec 18, 2013 3:41:28 AM)
I looked at the code. The logic was :
1) (source hbase up and peer hbase down) delete some rows from source on two
tables: t1_syncup,t2_syncup
2) (shutdown source, bring up peer). run syncup
3) count on peer cluster, t1_syncup verified correctly, but t2_syncup failed as
it didn't get the 'delete' transactions.
I am looking into it.
Demai
> Intermittent TestReplicationSyncUpTool failure
> ----------------------------------------------
>
> Key: HBASE-10189
> URL: https://issues.apache.org/jira/browse/HBASE-10189
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Demai Ni
> Fix For: 0.98.0, 0.94.15, 0.96.2, 0.99.0
>
> Attachments: 10189-0.94.txt, 10189-test-sync-tool.html,
> HBASE-10189-0.94-v0.patch, HBASE-10189-trunk-v0.patch
>
>
> From https://builds.apache.org/job/PreCommit-HBASE-Build/8200//testReport/ :
> {code}
> java.lang.AssertionError: t2_syncup has 201 rows on source, and 200 on slave1
> expected:<200> but was:<125>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at
> org.apache.hadoop.hbase.replication.TestReplicationSyncUpTool.putAndReplicateRows(TestReplicationSyncUpTool.java:245)
> at
> org.apache.hadoop.hbase.replication.TestReplicationSyncUpTool.testSyncUpTool(TestReplicationSyncUpTool.java:116)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
