Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 6 Apr 2015 18:18:13 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12787860.1428021359000.5345.1428344293876@Atlassian.JIRA>
In-Reply-To: <JIRA.12787860.1428021359000@Atlassian.JIRA>
References: <JIRA.12787860.1428021359000@Atlassian.JIRA>
 <JIRA.12787860.1428021359754@arcas>
Subject: [jira] [Commented] (HBASE-13391) TestRegionObserverInterface
 frequently failing on branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sean Busbey commented on HBASE-13391:
-------------------------------------

{quote}
bq. 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.

I was thinking that we could turn off distributed replay, to achieve the same aim as adding code to the test to wait for replay to finish. However then the test fails with "got 3 expected 1".
{quote}

I think with DLR off it would just expand the window of the race condition, unless the test tries to scan to check that the region is available or something like that. Does the "got 3 expect 1" thing happen on master as well? Sounds like we should break it off into a different jira. If the failure isn't pressing I'll take that new jira (barring a shift in severity, I don't expect to be able to look at it until next week).

> 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)