[
https://issues.apache.org/jira/browse/YARN-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993711#comment-14993711
]
Steve Loughran commented on YARN-4330:
--------------------------------------
+1 for downgrading the stack trace to DEBUG level; anything at INFO/WARN should
include the calculator plugin conf value in case that is the problem.
and another +1 for having a way to turn this off for minicluster tests. Having
a dummy plugin would be more generally useful, and avoid having yet another
config option
> 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
> Assignee: Varun Saxena
> 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)
