[
https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447827#comment-13447827
]
Himanshu Vashishtha commented on HBASE-6714:
--------------------------------------------
Since we are interested in seeing whether a row is replicated while log is
rolled, we can add a method checkAndWait to see if it is replicated.
> 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
>
> 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
