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. Signed-off-by: Ted Yu <tedyu@apache.org>
This commit is contained in:
parent
b0b6064293
commit
6f0c9fbfd1
|
@ -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;
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue