You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Wang Zhefeng (JIRA)" <ji...@apache.org> on 2019/01/18 10:28:00 UTC

[jira] [Commented] (LIVY-550) Batch Session will stay in state starting when some error happened in spark-submit process

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

Wang Zhefeng commented on LIVY-550:
-----------------------------------

I try to solve it, and submit a PR：https://github.com/apache/incubator-livy/pull/140

> Batch Session will stay in state starting when some error happened in spark-submit process
> ------------------------------------------------------------------------------------------
>
>                 Key: LIVY-550
>                 URL: https://issues.apache.org/jira/browse/LIVY-550
>             Project: Livy
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.5.0
>            Reporter: Wang Zhefeng
>            Priority: Major
>             Fix For: 0.6.0
>
>
> For example：when user input wrong username or queue，and submit a batch session。it will throw error in spark-submit process, but batch session state won't change because batch session state change depends on SparkApp state change. So this session will become dead until livy.server.yarn.app-leakage.check-timeout overdued， in my env，it's 600s. I think in this case should have a quick failure.



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