You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/10/01 20:39:00 UTC

[jira] [Resolved] (LIVY-520) Log when a session is deleted because of timeout

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

Marcelo Vanzin resolved LIVY-520.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.6.0

Issue resolved by pull request 116
[https://github.com/apache/incubator-livy/pull/116]

> Log when a session is deleted because of timeout
> ------------------------------------------------
>
>                 Key: LIVY-520
>                 URL: https://issues.apache.org/jira/browse/LIVY-520
>             Project: Livy
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 0.6.0
>            Reporter: Marco Gaido
>            Priority: Minor
>             Fix For: 0.6.0
>
>
> When a session is idle for more than {{livy.server.session.timeout}} it is GCed, ie. it is closed. But there is no evidence that this is the reason why the session is closed, so it may be non-trivial to detect the reason why the session was closed.
> This JIRA proposes to add a log information when a session is GCed in order to make it clearer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)