-
Notifications
You must be signed in to change notification settings - Fork 346
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
Should the idle culler also cull named servers? #547
Comments
Although it looks like they should be taken into account by the idle culler:
|
Maybe this change to the cull idle script used by Z2JH is helpful jupyterhub/zero-to-jupyterhub-k8s#1558 |
Thanks @betatim for the pointer! |
It looks like the Then adding a new |
Looking into jupyterhub/zero-to-jupyterhub-k8s#1558, it seems like this change is about deleting the named server rather than stopping? |
Fixed by #559. |
Testing a TLJH deployment with:
It looks like the default server is correctly culled after it has been idle for more than the number specified in
timeout
,However the named servers are still shown as running in the list of servers and can be accessed normally, and they don't appear to be culled.
Should the idle culler script also take into account the named servers?
The text was updated successfully, but these errors were encountered: