From 46ca0dbba60942866c5a9a8832e2f9a3608e1cb0 Mon Sep 17 00:00:00 2001 From: xicm <36392121+xicm@users.noreply.github.com> Date: Thu, 10 Mar 2022 16:06:12 +0800 Subject: [PATCH] HBASE-26815 TestFanOutOneBlockAsyncDFSOutput is flakey (#4186) Trigger BlockReports in MiniDFSCluster after restarting datanode Signed-off-by: Duo Zhang --- .../hbase/io/asyncfs/TestFanOutOneBlockAsyncDFSOutput.java | 2 ++ 1 file changed, 2 insertions(+) diff --git a/hbase-asyncfs/src/test/java/org/apache/hadoop/hbase/io/asyncfs/TestFanOutOneBlockAsyncDFSOutput.java b/hbase-asyncfs/src/test/java/org/apache/hadoop/hbase/io/asyncfs/TestFanOutOneBlockAsyncDFSOutput.java index 8533d38bae09..abdba33b8033 100644 --- a/hbase-asyncfs/src/test/java/org/apache/hadoop/hbase/io/asyncfs/TestFanOutOneBlockAsyncDFSOutput.java +++ b/hbase-asyncfs/src/test/java/org/apache/hadoop/hbase/io/asyncfs/TestFanOutOneBlockAsyncDFSOutput.java @@ -220,6 +220,7 @@ public void testConnectToDatanodeFailed() assertEquals(2, output.getPipeline().length); } finally { CLUSTER.restartDataNode(dnProp); + CLUSTER.triggerBlockReports(); } } @@ -250,6 +251,7 @@ public void testExcludeFailedConnectToDatanode() assertEquals(1, excludeDatanodeManager.getExcludeDNs().size()); } finally { CLUSTER.restartDataNode(dnProp); + CLUSTER.triggerBlockReports(); } }