[ https://issues.apache.org/jira/browse/LIVY-515 ]
Larry McCay deleted comment on LIVY-515:
----------------------------------
was (Author: lmccay):
Due to the pending 2.0.0 release this JIRA has been pushed out to 2.1.0 as part
of a bulk update. If there is a specific reason to pull this back into the
2.0.0 release and you intend to provide a PR in the next few days please
provide justification and reset the Fix Version to 2.0.0.
> Livy session is idle even if spark context is unavailable
> ---------------------------------------------------------
>
> Key: LIVY-515
> URL: https://issues.apache.org/jira/browse/LIVY-515
> Project: Livy
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.4.0
> Reporter: Raghavendra
> Priority: Major
> Fix For: 0.9.0
>
> Attachments: AfterKillingLivy.png, BeforeKillingLivy.png,
> command.history, livy-log, livyUI.png
>
>
> When using livy in the session mode, Livy is not able to figure out if the
> application master is available.
> Say suppose livy was in the idle state, now for some reason the application
> master died. Ideally, even the session associated with this application
> master should either be terminated or should have handled this situation.
> Instead, the session continues to remain in the Idle state. This is wrong.
>
> Steps to reproduce.
> # Bring up livy in session mode(I am using 5 sessions).
> # Kill the application master using "yarn application -kill <application id>"
> # Now list the application in yarn "yarn application -list" you will see 4
> application master(I had 5, Killed 1 so 4)
> # Now reload livy UI. You will still see 5 sessions in idle.
> Attached the session logs whose application master was killed.
> Attached are some images depicting the issue
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
