You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Saisai Shao (Jira)" <ji...@apache.org> on 2019/09/17 09:24:00 UTC

[jira] [Resolved] (LIVY-633) session should not be gc-ed for long running queries

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

Saisai Shao resolved LIVY-633.
------------------------------
    Fix Version/s: 0.7.0
         Assignee: Yiheng Wang
       Resolution: Fixed

Issue resolved by pull request 224
https://github.com/apache/incubator-livy/pull/224

> session should not be gc-ed for long running queries
> ----------------------------------------------------
>
>                 Key: LIVY-633
>                 URL: https://issues.apache.org/jira/browse/LIVY-633
>             Project: Livy
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.6.0
>            Reporter: Liju
>            Assignee: Yiheng Wang
>            Priority: Major
>             Fix For: 0.7.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> If you have set a relatively small session timeout eg 15 mins and query execution is taking > 15 mins , the session gets gc-ed , which is incorrect wrt user experience as the user was still active on session and waiting for result



--
This message was sent by Atlassian Jira
(v8.3.2#803003)