You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Gyorgy Gal (Jira)" <ji...@apache.org> on 2025/11/10 17:13:03 UTC

[jira] [Updated] (LIVY-139) Livy server needs notification when remote session dies

     [ https://issues.apache.org/jira/browse/LIVY-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyorgy Gal updated LIVY-139:
----------------------------
    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.

> Livy server needs notification when remote session dies
> -------------------------------------------------------
>
>                 Key: LIVY-139
>                 URL: https://issues.apache.org/jira/browse/LIVY-139
>             Project: Livy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.2
>            Reporter: Marcelo Masiero Vanzin
>            Priority: Major
>             Fix For: 0.10.0
>
>
> Currently, when the remote context for some reason dies and loses its connection to the Livy server, there's no event that the server receives and can act upon to mark the session as dead or clean it up.
> We need to add that, also so that users don't get ugly errors when sending commands to those sessions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)