[
https://issues.apache.org/jira/browse/LIVY-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916958#comment-16916958
]
Igor Calabria commented on LIVY-633:
[~yihengw] I believe this is a separate issue. The one you linked fixed the
case where even busy sessions were killed. In this one, the session is killed
after it completes a statement that takes longer than the timeout. It seems
that `Session#recordActivity()`
[https://github.com/apache/incubator-livy/blob/master/server/src/main/scala/org/apache/livy/sessions/Session.scala#L176]
is not called when the statement finishes, so when the session transitions
from busy to idle, it'll be instantly destroyed.
> 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
>Priority: Major
>
> 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)
