Hi Jafar. Adding to Roland's questions... Per the attached config file, you have not enabled culling. The culling options that you have apparently modified are still commented out. Remove the comment character for those options to 'activate' them. In addition, there may be other steps involved for "exposing" Notebook configuration files within a JupyterHub environment. (I'm unfamiliar with Hub so perhaps others can confirm.) Finally, I believe Hub may have (or is in the process of having) the capability to cull the spawned Notebook servers. If I recall the various threads of conversation on this, I think Hub's culling of Notebook servers also considers the notebook server's kernel's idle time. However, what I'm not certain about is if the culling of Notebook servers (by Hub) is dependent on enablement of the culling of kernels within the Notebook server vs. a different Hub-scoped configuration option for culling the spawned NB server.
On Thursday, February 7, 2019 at 5:57:03 AM UTC-8, Jafar Sharif wrote: > > Hi Roland, > Let explain you my case for achieving it. We have jupyterhub in an > aws instance and have different logins for different user, Sometimes we > all work on the same user and people will start working on the tasks and > in the end of the they will close the notebook without shutdown. In this > case it is consuming the most of the instance . so i am thinking of is > there anyway to kill the kernals that are running for long hours(idle > kernels). So i have seen in the jupyter notebook documentation from 5.1.0 > they have introduced the killing of the kernels through config file.With > the help of documentation file i have generated the config file and made > changes as per the documentation. My current jupyter version is 5.7.1.. Can > you please let me know what changes need to be done in the config file. I > have attached the config file. > > Thanks > Jafar > > On Thu, Feb 7, 2019 at 12:23 PM Roland Weber <[email protected] > <javascript:>> wrote: > >> Have you checked that you're on a recent version of Jupyter Notebook? >> >> Are the kernels actually idle, or could they still be executing a >> long-running cell? >> >> Have you tried to enable debug logging, to see if the culling is actually >> attempted? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Project Jupyter" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jupyter/b6e221e2-d955-4d32-8994-9f3029789623%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jupyter/b6e221e2-d955-4d32-8994-9f3029789623%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/6f664394-38d1-4d52-9f9c-470e02323145%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
