[
https://issues.apache.org/jira/browse/LIVY-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin updated LIVY-550:
--------------------------------
Fix Version/s: (was: 0.6.0)
> 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
>
> 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)
