[
https://issues.apache.org/jira/browse/LIVY-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928486#comment-16928486
]
Yiheng Wang commented on LIVY-664:
----------------------------------
In the code, it will stop the duplicated session when finding there're
duplicated names. In my test, I find the stop session may fail. I guess it may
due to some race condition. I'm looking into it.
Another suggestion I think it good. We should check the name duplication before
submitting the application. I'll raise a patch to fix that.
> Spark application still running when Livy session creating was rejected
> ------------------------------------------------------------------------
>
> Key: LIVY-664
> URL: https://issues.apache.org/jira/browse/LIVY-664
> Project: Livy
> Issue Type: Bug
> Reporter: Oleksandr Shevchenko
> Priority: Major
> Attachments: image-2019-09-08-20-38-50-195.png,
> image-2019-09-08-20-39-18-569.png
>
>
> Steps for reproduce:
> 1. Create a session with some name
> 2. Create a second session with the same name
> 2.1 Second session creating will be rejected since duplicated session name
> is not allowed.
> 2.2 Spark application will be submitted but Livy session won't be created
>
> Result: Spark application was submitted but Livy session is not created
> Expected result: Livy session creating rejected AND Spark application should
> be finished with failed or killed state or even should not be submitted.
> !image-2019-09-08-20-38-50-195.png!
> !image-2019-09-08-20-39-18-569.png!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
