[
https://issues.apache.org/jira/browse/HBASE-28274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balazs Meszaros resolved HBASE-28274.
-------------------------------------
Fix Version/s: 2.6.0
2.4.18
3.0.0-beta-1
2.5.8
Resolution: Fixed
> Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)
> -----------------------------------------------------
>
> Key: HBASE-28274
> URL: https://issues.apache.org/jira/browse/HBASE-28274
> Project: HBase
> Issue Type: Test
> Components: flakies, integration tests, test
> Reporter: Andor Molnar
> Assignee: Andor Molnar
> Priority: Major
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> The following test sometimes fails for me when running locally with Maven:
> TestFanOutOneBlockAsyncDFSOutput.testRecover()
> I can't really figure out the reason, but it's probably a side effect of the
> preceding test: testConnectToDatanodeFailed(). This test also restarts one of
> the datanodes in the MiniDFS cluster just like testRecover() and it somehow
> causes the failure.
> {noformat}
> java.lang.AssertionError: flush should fail
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){noformat}
> The flush() call is testRecover() should fail, because we restart one of the
> DN in the DFS cluster which is expected to brake connection. It succeeds
> though if the preceding test already restarted a DN. No matter which DN we
> restart, even if they're different, the error occurs.
> I also tried to add CLUSTER.waitDatanodeFullyStarted() at the end of
> testConnectToDatanodeFailed(), looks like it made the tests slightly more
> stable, but didn't help fully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
