You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@livy.apache.org by GitBox <gi...@apache.org> on 2019/01/24 20:08:29 UTC

[GitHub] vanzin commented on issue #138: [LIVY-547]do not check expire when session in state busy

vanzin commented on issue #138: [LIVY-547]do not check expire when session in state busy
URL: https://github.com/apache/incubator-livy/pull/138#issuecomment-457338491
 
 
   I don't remember exactly how the clients monitor interactive sessions, but doesn't a client poll for the result of a statement? Doesn't that count as updating the session for activity?
   
   Although I guess that would still not account for the "fire a job and go out for a few days" use case.
   
   It sounds like a separate config is the only way to cover all user cases (e.g. a "busy timeout", which by default maintains the current behavior, and can be set to stop the session if it's been busy for a certain period).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services