hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4330) MiniYARNCluster is showing multiple Failed to instantiate default resource calculator warning messages.
Date Tue, 15 Nov 2016 12:01:06 GMT

    [ https://issues.apache.org/jira/browse/YARN-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666962#comment-15666962

Varun Saxena commented on YARN-4330:

Agree... I was under the impression that we get Resource calculator plugin by passing the
relevant class name in NodeManagerHardwareUtils but we do not in current code. It is passed
from the caller i.e. primarily from ContainersMonitorImpl. So if something specific has to
be done to load Node resource monitor plugin, that should be done in another JIRA.

> MiniYARNCluster is showing 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
>              Labels: oct16-hard
>         Attachments: YARN-4330.002.patch, YARN-4330.003.patch, YARN-4330.01.patch
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message