[
https://issues.apache.org/jira/browse/OOZIE-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890154#comment-16890154
]
Peter Bacsko edited comment on OOZIE-3512 at 7/22/19 3:37 PM:
--------------------------------------------------------------
Usually an application stays in ACCEPTED state if there are not enough
resources (vcores / memory). Another problem is when a node manager becomes
UNHEALTHY - we set up the Mini YARN cluster with a single NM cluster, so if
that happens, we can't run any applications. This happened many times before
due to disk space issues and the disk checker, having detected a low amount of
free space, marked the NM as "unhealthy" so we ended up with 0 NMs. But this
was addressed and the threshold was raised to 99% or 100%. Anyway I'd examine
the RM or NM output from the Mini cluster to see why this wasn't scheduled.
was (Author: pbacsko):
Usually an application stays in ACCEPTED state if there are not enough
resources (vcores / memory). Another problem is when a node manager becomes
UNHEALTHY - we set up the Mini YARN cluster with a single NM cluster, so if
that happens, we can't run any applications. This happened many times before
due to disk space issues and the disk checker, having detected a low amount of
free space, marked the NM as "unhalthy" so we ended up with 0 NMs. But this was
addressed and the threashold was raised to 99% or 100%. Anyway I'd examine the
RM or NM output from the Mini cluster to see why this wasn't scheduled.
> Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA
> ----------------------------------------------------------------------
>
> Key: OOZIE-3512
> URL: https://issues.apache.org/jira/browse/OOZIE-3512
> Project: Oozie
> Issue Type: Sub-task
> Components: tests
> Affects Versions: trunk
> Reporter: Andras Salamon
> Assignee: duan xiong
> Priority: Major
>
> {{TestActionStartXCommand.testActionWithEscapedStringAndCDATA}} is flaky,
> sometimes (for instance:
> https://issues.apache.org/jira/browse/OOZIE-3470?focusedCommentId=16817901&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16817901
> ) it fails with the following error message:
> {noformat}junit.framework.AssertionFailedError: YARN App state for app
> application_1559489642789_0018 expected:<FINISHED> but was:<ACCEPTED>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.oozie.test.XTestCase.waitUntilYarnAppDoneAndAssertSuccess(XTestCase.java:1358)
> at
> org.apache.oozie.command.wf.TestActionStartXCommand.testActionWithEscapedStringAndCDATA(TestActionStartXCommand.java:235)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
