Andras Salamon created OOZIE-3503:
-------------------------------------

             Summary: TestJavaActionExecutor.testSubmitWithLauncherQueue unit 
test failure
                 Key: OOZIE-3503
                 URL: https://issues.apache.org/jira/browse/OOZIE-3503
             Project: Oozie
          Issue Type: Bug
          Components: tests
            Reporter: Andras Salamon
            Assignee: Andras Salamon


{{TestJavaActionExecutor.testSubmitWithLauncherQueue}} unit test fails if 
CapacityScheduler is strict and does not allow to use unknown queues. It gives 
the following error:

{noformat}org.apache.oozie.action.ActionExecutorException: YarnException: 
Failed to submit application_1559057153957_0057 to YARN : Application 
application_1559057153957_0057 submitted by user test to unknown queue: test
        at 
org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:452)
        at 
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1103)
        at 
org.apache.oozie.action.hadoop.TestJavaActionExecutor.submitAction(TestJavaActionExecutor.java:375)
        at 
org.apache.oozie.action.hadoop.TestJavaActionExecutor.submitAction(TestJavaActionExecutor.java:387)
        at 
org.apache.oozie.action.hadoop.TestJavaActionExecutor.testSubmitWithLauncherQueue(TestJavaActionExecutor.java:2588)
...
Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
application_1559057153957_0057 to YARN : Application 
application_1559057153957_0057 submitted by user test to unknown queue: test
        at 
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:322)
        at 
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1091)
        ... 45 more
{noformat}

We should use a queue name which is listed in the 
{{yarn.scheduler.capacity.root.queues}} property ( 
https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/test/XTestCase.java#L1109
 ) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to