From f12e6be3c37d4cfc9aa054f14f6c36b7bfc8988b Mon Sep 17 00:00:00 2001 From: Josh Elser Date: Tue, 21 Nov 2017 13:42:13 -0500 Subject: [PATCH] HBASE-19317 Set a high NodeManager max disk utilization if not already set This avoids the situation where the build machine has sufficient disk space (a few GB's at most) to run an HBase test, but the default YARN configuration would preclude the NM's from starting correctly. This should eliminate a trivial source of build flakiness based on the host machines being used. --- .../src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java b/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java index bb7eca2caf..eec78920eb 100644 --- a/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java +++ b/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java @@ -2552,6 +2552,10 @@ public class HBaseTestingUtility extends HBaseCommonTestingUtility { * @throws IOException When starting the cluster fails. */ public MiniMRCluster startMiniMapReduceCluster() throws IOException { + // Set a very high max-disk-utilization percentage to avoid the NodeManagers from failing. + conf.setIfUnset( + "yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage", + "99.0"); startMiniMapReduceCluster(2); return mrCluster; } -- 2.14.1