hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4330) MiniYARNCluster is showing multiple Failed to instantiate default resource calculator warning messages.
Date Tue, 25 Oct 2016 20:48:58 GMT

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

Eric Badger commented on YARN-4330:
-----------------------------------

I applied the most recent patch the branch-2.8 and ran {{TestMRTimelineEventHandling}}, which
uses the MiniYARNCluster (I'm running MacOS Sierra). 2 of the 3 tests in the class consistently
fail with the stacktraces as shown below. I didn't dig into the tests any further, but I imagine
that this is reproducible on other machines. 

{noformat}
Running org.apache.hadoop.mapred.TestMRTimelineEventHandling
Tests run: 3, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 93.809 sec <<< FAILURE!
- in org.apache.hadoop.mapred.TestMRTimelineEventHandling
testMRTimelineEventHandling(org.apache.hadoop.mapred.TestMRTimelineEventHandling)  Time elapsed:
35.821 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<3>
	at org.apache.hadoop.mapred.TestMRTimelineEventHandling.testMRTimelineEventHandling(TestMRTimelineEventHandling.java:105)

testMapreduceJobTimelineServiceEnabled(org.apache.hadoop.mapred.TestMRTimelineEventHandling)
 Time elapsed: 32.703 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<3>
	at org.apache.hadoop.mapred.TestMRTimelineEventHandling.testMapreduceJobTimelineServiceEnabled(TestMRTimelineEventHandling.java:162)
{noformat}

> 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
>         Attachments: 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
(v6.3.4#6332)

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


Mime
View raw message