[
https://issues.apache.org/jira/browse/HBASE-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481492#comment-14481492
]
Sean Busbey commented on HBASE-13391:
-------------------------------------
If there's still recovery happening then that would explain the "saw 0"
failure.Does the test actually attempt to verify that replay is done?
Is the failure log with distributed log replay off? I'll have to dig in some to
figure out what would lead to seeing 3x the recovery. nothing obvious comes to
mind. The part I don't understand is why we'd get different numbers for the
non-legacy and the legacy version, given that they get called in the same loop.
> TestRegionObserverInterface frequently failing on branch-1
> -----------------------------------------------------------
>
> Key: HBASE-13391
> URL: https://issues.apache.org/jira/browse/HBASE-13391
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 1.1.0
>
> Attachments: test.log.fail.txt, test.log.pass.txt
>
>
> TestRegionObserverInterface is frequently failing on branch-1 .
> Example:
> {noformat}
> java.lang.AssertionError: Result of
> org.apache.hadoop.hbase.coprocessor.SimpleRegionObserver$Legacy.getCtPreWALRestore
> is expected to be 1, while we get 0
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.verifyMethodResult(TestRegionObserverInterface.java:751)
> at
> org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.testLegacyRecovery(TestRegionObserverInterface.java:685)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
