[
https://issues.apache.org/jira/browse/HBASE-12771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265515#comment-14265515
]
Manukranth Kolloju commented on HBASE-12771:
--------------------------------------------
Currently, by killing a regionserver other than META seems to be behaving
properly. The test ran about 100 times and passed all the times, so the fix
seems to have brought back the trunk behavior.
Here the request is being made from a client in the unit test, so, I am not
sure what would be significantly different just because the META is colocated
with the master. I will spend some more time to understand why we are seeing
unnecessary sleeps in branch 1 during meta lookup, but the test failures can be
explained purely by the extra delays which I did not account for in the test.
> TestFailFast#testFastFail failing
> ---------------------------------
>
> Key: HBASE-12771
> URL: https://issues.apache.org/jira/browse/HBASE-12771
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 1.0.0
> Reporter: stack
> Assignee: Manukranth Kolloju
>
> Fails on our internal rig and from time to time on apache. Here is latest:
> {code}
> org.apache.hadoop.hbase.client.TestFastFail.testFastFail
> Failing for the past 1 build (Since Failed#654 )
> Took 7.1 sec.
> Error Message
> Only few thread should ideally be waiting for the dead regionserver to be
> coming back. numBlockedWorkers:155 threads that retried : 10
> Stacktrace
> java.lang.AssertionError: Only few thread should ideally be waiting for the
> dead regionserver to be coming back. numBlockedWorkers:155 threads that
> retried : 10
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.hadoop.hbase.client.TestFastFail.testFastFail(TestFastFail.java:270)
> {code}
> Opening this issue so can start tracking the fails. Looking in log, nothing
> obvious. Will be back to this one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
