You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Wing Yew Poon (Jira)" <ji...@apache.org> on 2020/03/09 18:35:00 UTC

[jira] [Comment Edited] (LIVY-576) Unknown YARN state RUNNING for app with final status SUCCEEDED

    [ https://issues.apache.org/jira/browse/LIVY-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055293#comment-17055293 ] 

Wing Yew Poon edited comment on LIVY-576 at 3/9/20, 6:34 PM:
-------------------------------------------------------------

I agree with [~shanyu] that it would be helpful if attention is paid to JIRAs when a fix is submitted. In this case, I see that a patch file is uploaded but I don't see a PR. Maybe that is why the fix was neglected?



was (Author: wypoon):
I agree with [~shanyu] that it would be helpful if attention is paid to JIRAs when a fix is submitted. In this case, I see that a patch file is uploaded but I don't see a PR. Maybe that is while the fix was neglected?


> 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
>             Fix For: 0.7.0
>
>         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)