[jira] [Commented] (OOZIE-3503) TestJavaActionExecutor.testSubmitWithLauncherQueue unit test failure
[
https://issues.apache.org/jira/browse/OOZIE-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851839#comment-16851839
]
Julia Kinga Marton commented on OOZIE-3503:
---
Thank you [~asalamon74] for fixing this! +1, committed to master.
> 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
>Priority: Major
> Attachments: OOZIE-3503-01.patch
>
>
> {{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)
[jira] [Commented] (OOZIE-3503) TestJavaActionExecutor.testSubmitWithLauncherQueue unit test failure
[
https://issues.apache.org/jira/browse/OOZIE-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851028#comment-16851028
]
Hadoop QA commented on OOZIE-3503:
--
Testing JIRA OOZIE-3503
Cleaning local git 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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch 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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [core].
{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: 3169
{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/PreCommit-OOZIE-Build/1131/
> 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
>Priority: Major
> Attachments: OOZIE-3503-01.patch
>
>
> {{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
[jira] [Commented] (OOZIE-3503) TestJavaActionExecutor.testSubmitWithLauncherQueue unit test failure
[
https://issues.apache.org/jira/browse/OOZIE-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850901#comment-16850901
]
Hadoop QA commented on OOZIE-3503:
--
PreCommit-OOZIE-Build started
> 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
>Priority: Major
> Attachments: OOZIE-3503-01.patch
>
>
> {{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)
