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/17 22:16:54 UTC

[GitHub] meisam edited a comment on issue #138: [LIVY-547]do not check expire when session in state busy

meisam edited a comment on issue #138: [LIVY-547]do not check expire when session in state busy
URL: https://github.com/apache/incubator-livy/pull/138#issuecomment-455352091
 
 
   > or may you share me some counter-cases
   
   
   If the number of jobs running are small and can be monitored manually, it makes sense to keep busy jobs.
   But in a system with hundreds of users and thousands of jobs running each day, it is impractical to check the status of each job manually. In many cases, users submit jobs on a daily/hourly basis though an enterprise scheduler. In this case, if a job takes too long to run, it is better to fail it and figure out why it took so long.
   Also, users have the option to keep the jobs alive by reset the last activity time for a job though the `sessions/:id/connect` endpoint.

----------------------------------------------------------------
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