From 1c3d19087d29e2c65114726e1a66678157bb4dfa Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Thu, 19 Oct 2023 13:36:33 +0200 Subject: [PATCH 1/3] Update docs about max-age culling, now 7 days --- admin/howto/control-user-server.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/admin/howto/control-user-server.md b/admin/howto/control-user-server.md index e41dad1..77607cd 100644 --- a/admin/howto/control-user-server.md +++ b/admin/howto/control-user-server.md @@ -79,15 +79,24 @@ Active notebooks have their kernel killed as well. To ensure efficient resource usage, user servers without interactive usage for a period of time (default `1h`) are automatically stopped (via -[jupyterhub-idle-culler](https://github.com/jupyterhub/jupyterhub-idle-culler)). -This means your notebook server might be stopped for inactivity even if you have +[jupyterhub-idle-culler]). +This means your user server might be stopped for inactivity even if you have a long running process in the notebook. This timeout can be configured. % TODO: Add link to SRE guide on how to configure this, once it exists -Culling has the same effect as [stopping a user's server](user-server/stopping). +"Culling a user server" has the same effect as [stopping a user +server](user-server/stopping), but should be distinguished from "culling a +kernel" inside a user server. [jupyterhub-idle-culler] is only involved in +culling user servers, not culling kernels. -There is currently no maximum time limit for a user's notebook. +## Stop user servers after maximum age + +As a failsafe [jupyterhub-idle-culler] is by 2i2c's defaults configured to stop +user servers that has been running for more than 7 days. This max age can be +re-configured. + +[jupyterhub-idle-culler]: https://github.com/jupyterhub/jupyterhub-idle-culler ## Stop user kernels after inactivity From 5a698e0ca18271a9c8b08f82c1192fee0289b8c8 Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Thu, 19 Oct 2023 13:37:09 +0200 Subject: [PATCH 2/3] Add note about workaround to avoid culling by inactivity --- admin/howto/control-user-server.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/admin/howto/control-user-server.md b/admin/howto/control-user-server.md index 77607cd..fedfa2a 100644 --- a/admin/howto/control-user-server.md +++ b/admin/howto/control-user-server.md @@ -90,6 +90,11 @@ server](user-server/stopping), but should be distinguished from "culling a kernel" inside a user server. [jupyterhub-idle-culler] is only involved in culling user servers, not culling kernels. +```{note} +A crude way to ensure that a server isn't stopped for inactivity is can be read +about [here](https://github.com/jupyterhub/jupyterhub-idle-culler/issues/55#issuecomment-1413510651). +``` + ## Stop user servers after maximum age As a failsafe [jupyterhub-idle-culler] is by 2i2c's defaults configured to stop From a8d4d2c2c15cee88c4cbf992f1d1913b3e66dccf Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Thu, 19 Oct 2023 15:10:30 +0200 Subject: [PATCH 3/3] Make link title be more informative than "here" Co-authored-by: Sarah Gibson <44771837+sgibson91@users.noreply.github.com> --- admin/howto/control-user-server.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/admin/howto/control-user-server.md b/admin/howto/control-user-server.md index fedfa2a..4c1b005 100644 --- a/admin/howto/control-user-server.md +++ b/admin/howto/control-user-server.md @@ -91,8 +91,7 @@ kernel" inside a user server. [jupyterhub-idle-culler] is only involved in culling user servers, not culling kernels. ```{note} -A crude way to ensure that a server isn't stopped for inactivity is can be read -about [here](https://github.com/jupyterhub/jupyterhub-idle-culler/issues/55#issuecomment-1413510651). +A crude way to [ensure that a server isn't stopped for inactivity](https://github.com/jupyterhub/jupyterhub-idle-culler/issues/55#issuecomment-1413510651) can be implemented. ``` ## Stop user servers after maximum age