[
https://issues.apache.org/jira/browse/LIVY-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-550:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.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: Zhefeng Wang
> Priority: Major
> Fix For: 0.10.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
(v8.20.10#820010)
