You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/11/04 18:58:28 UTC
[jira] [Created] (YARN-4330) MiniYARNCluster prints multiple
Failed to instantiate default resource calculator warning messages
Steve Loughran created YARN-4330:
------------------------------------
Summary: MiniYARNCluster prints multiple Failed to instantiate default resource calculator warning messages
Key: YARN-4330
URL: https://issues.apache.org/jira/browse/YARN-4330
Project: Hadoop YARN
Issue Type: Bug
Components: test, yarn
Affects Versions: 2.8.0
Environment: OSX, JUnit
Reporter: Steve Loughran
Priority: Blocker
Whenever I try to start a MiniYARNCluster on Branch-2 (commit #0b61cca), I see multiple stack traces warning me that a resource calculator plugin could not be created
{code}
(ResourceCalculatorPlugin.java:getResourceCalculatorPlugin(184)) - java.lang.UnsupportedOperationException: Could not determine OS: Failed to instantiate default resource calculator.
java.lang.UnsupportedOperationException: Could not determine OS
{code}
This is a minicluster. It doesn't need resource calculation. It certainly doesn't need test logs being cluttered with even more stack traces which will only generate false alarms about tests failing.
There needs to be a way to turn this off, and the minicluster should have it that way by default.
Being ruthless and marking as a blocker, because its a fairly major regression for anyone testing with the minicluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)