Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document kernel culling #91

Merged
merged 3 commits into from
Aug 27, 2021
Merged

Document kernel culling #91

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
86de09a
Document kernel culling
GeorgianaElena Aug 26, 2021
5c5ddf4
Update admin/howto/control-user-server.md
choldgraf Aug 26, 2021
0d8df21
Update admin/howto/control-user-server.md
GeorgianaElena Aug 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions admin/howto/control-user-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,3 +72,16 @@ a long running process in the notebook. This timeout can be configured.
Culling has the same effect as [stopping a user's server](user-server/stopping).

There is currently no maximum time limit for a user's notebook.

## Stop user kernels after inactivity

In addition to the user _server_, there may also be culling at the _kernel_ level.
The kernel is the thing that actually "runs code", and a kernel without any activity for some time means that somebody has not executed code in that time.

By default, kernels will be checked for activity **every `5 minutes`**.
All kernels that haven't shown activity in **in the last hour** will be stopped by the [jupyterhub-idle-culler](https://github.com/jupyterhub/jupyterhub-idle-culler).

This window can be configured if you'd like to change the window of inactivity needed before user kernels will be stopped.
See the [Hub Engineer's guide](ph:configure:culling) for some documentation on this.

% TODO: Add link to SRE guide on how to configure this, once it exists