You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 tojhsingle_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:
Anything else?
No response
The text was updated successfully, but these errors were encountered: