Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Config option to shut down server after N seconds with no kernels #2963
This is something I was discussing with @minrk yesterday: allow the notebook server to shut down automatically after some time with no kernels active. This could be useful with nbopen: a notebook server can be started automatically when you double-click a notebook file, and then clean itself up automatically when you've finished using it.
This is not yet ready for merge: I think it should take all activity into account for the timeout, not just kernel activity, so it doesn't shut down while you're editing a file or using a terminal. It will probably be a few days before I have time to finish it off.
This is now ready for review: it considers kernels, terminals and API activity, so it shouldn't shut the server down if you're still doing anything.
You could configure it like this:
c.MappingKernelManager.cull_idle_timeout = 600 c.NotebookApp.shutdown_no_activity_timeout = 600
With those options, if you close a notebook tab leaving the kernel running, it will cull the kernel after 10 minutes. After another 10 minutes, if you haven't done anything else, the server will shut down.
There is currently no option to cull idle terminals, so if you leave a terminal open, the server will never shut down. We could add an option for that separately.
Makes sense. Only thing I'd like to add is that there's already an API endpoint for retrieving activity info in