[
https://issues.apache.org/jira/browse/OOZIE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482740#comment-13482740
]
Hadoop QA commented on OOZIE-1029:
----------------------------------
Testing JIRA OOZIE-1029
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
. Tests run: 914
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/156/
> MiniMRCluster fails to start when used against YARN
> ---------------------------------------------------
>
> Key: OOZIE-1029
> URL: https://issues.apache.org/jira/browse/OOZIE-1029
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-1029.patch
>
>
> When using YARN (via invoking maven with -Phadoop-3), any tests using the
> MiniMRCluster get an error because MiniMRCluster fails to start.
> For example:
> {code}
> org.apache.hadoop.yarn.YarnException: Failed to Start
> org.apache.hadoop.mapred.MiniMRCluster
> at
> org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:78)
> at
> org.apache.hadoop.mapred.MiniMRClientClusterFactory.create(MiniMRClientClusterFactory.java:71)
> at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:180)
> at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:170)
> at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:162)
> at
> org.apache.oozie.test.XTestCase.setUpEmbeddedHadoop(XTestCase.java:725)
> at org.apache.oozie.test.XTestCase.setUp(XTestCase.java:281)
> at org.apache.oozie.test.XFsTestCase.setUp(XFsTestCase.java:58)
> ...
> Caused by: org.apache.hadoop.yarn.YarnException:
> java.lang.IllegalStateException: Queue configuration missing child queue
> names for root
> at
> org.apache.hadoop.yarn.server.MiniYARNCluster$ResourceManagerWrapper.start(MiniYARNCluster.java:184)
> at
> org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:68)
> ... 26 more
> Caused by: java.lang.IllegalStateException: Queue configuration missing child
> queue names for root
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:307)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:232)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:202)
> at
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.init(ResourceManager.java:201)
> at
> org.apache.hadoop.yarn.server.MiniYARNCluster$ResourceManagerWrapper.start(MiniYARNCluster.java:164)
> ... 27 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
