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

add single user server spawn delay and user-facing message #825

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

shaneknapp
Copy link
Contributor

@shaneknapp shaneknapp commented Mar 20, 2024

this PR allows admins to add a delay to single-user server spawns (useful for testing), and adds a configurable message to present to users after an amount of time has passed, imploring patience.

adding a delay was useful in debugging some grafana metrics (berkeley-dsep-infra/datahub#4237, berkeley-dsep-infra/datahub#4241).

the 'patience message' was added as users would believe that hubs were down/not working/etc when it took longer than a couple of minutes to launch their notebooks, particularly when a new GCP node was spinning up during peak usage times (berkeley-dsep-infra/datahub#3845, berkeley-dsep-infra/datahub#3963).

this has been incredibly useful for us at UC Berkeley and has saved both us and our users many hours of unnecessary support and debugging requests due to slow launches.

ref: #651

shaneknapp and others added 3 commits March 20, 2024 10:57
1) allows admins to add a delay to single-user server spawns (useful for testing)
2) adds a configurable message to present to users after an amount of time has passed, imploring patience
@shaneknapp
Copy link
Contributor Author

@yuvipanda @consideRatio

@manics
Copy link
Member

manics commented Jun 28, 2024

I'm not a fan of adding properties just for testing, especially since we already have a lot of complicated configuration properties, and it's trivial to add a delay by subclassing the spawner in-line in the Z2JH config.

A custom user message about the delay sounds useful though. Is there any way to put this in the parent class so it's available to all spawners, or is it inherently tied to KubeSpawner?

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

Successfully merging this pull request may close these issues.

2 participants