[
https://issues.apache.org/jira/browse/LIVY-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043920#comment-17043920
]
shanyu zhao commented on LIVY-576:
----------------------------------
Thanks [~andrasbeni], yes LIVY-642 is basically a duplicate of this JIRA with
exactly the same fix. We can close this JIRA now that LIVY-642 is checked in.
On the other hand, [~jerryshao], maybe we should be inspecting the JIRAs more
often. This JIRA has been sitting there for almost 1 year now without anyone
reviewing it. And a duplicate JIRA was reviewed and checked in after about 6
months.
> Unknown YARN state RUNNING for app with final status SUCCEEDED
> --------------------------------------------------------------
>
> Key: LIVY-576
> URL: https://issues.apache.org/jira/browse/LIVY-576
> Project: Livy
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.5.0
> Reporter: shanyu zhao
> Priority: Major
> Attachments: LIVY-576.patch
>
>
> Livy with Spark 2.3/2.4 on Yarn 2.9, there is a chance for Yarn to return
> application reports with Yarn state RUNNING and final Yarn status SUCCEEDED,
> this means the Yarn application is finishing up and about to be successful.
> Livy's mapYarnSate() method does not have a valid mapping for this
> combination and therefore it render the session 'dead'.
> I saw this in Livy server log:
> 19/03/25 20:04:28 ERROR utils.SparkYarnApp: Unknown YARN state RUNNING for
> app application_1553542555261_0063 with final status SUCCEEDED.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
