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.

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

Named Servers not being shut down by JupyterHub Idle Culler #136

Open
tylergraff opened this issue Feb 27, 2024 · 0 comments
Open

Named Servers not being shut down by JupyterHub Idle Culler #136

tylergraff opened this issue Feb 27, 2024 · 0 comments

Comments

@tylergraff
Copy link
Contributor

Context

Named servers are not being shut down by the JupyterHub Idle Culler, regardless of settings passed in through the nebari config.

I traced this issue to jhsingle_native_proxy default behavior of reporting "fake" server activity to JupyterHub to prevent its servers from being shut down by the JupyterHub idle culler. Passing the --no-force-alive flag to jhsingle_native_proxy disables this "fake" activity reporting, and allows the idle culler to operate as expected.

Value and/or benefit

Implementing this change will allow unused/idle servers spawned via jhsingle_native_proxy to be culled (depending on idle culler configuration), which will save compute resources.

This behavior can be shut off by utilizing the following override in the nebari config:

jupyterhub:
  overrides:
    cull:
      removeNamedServers: false

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant