[
https://issues.apache.org/jira/browse/LIVY-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghavendra updated LIVY-515:
-----------------------------
Description:
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 same.
was:
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 see 5 sessions.
Attached the session logs whose application master was killed.
Attached are some images depicting the same.
> 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
> Attachments: AfterKillingLivy.png, BeforeKillingLivy.png, 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 same.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
