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

Do we need 2 user- schedulers? #178

Open
asmacdo opened this issue Jul 24, 2024 · 0 comments
Open

Do we need 2 user- schedulers? #178

asmacdo opened this issue Jul 24, 2024 · 0 comments
Milestone

Comments

@asmacdo
Copy link
Member

asmacdo commented Jul 24, 2024

user-scheduler   2/2     2            2           5d2h   kube-scheduler   registry.k8s.io/kube-scheduler:v1.26.15   app=jupyterhub,component=user-scheduler,release=jupyterhub

The user-scheduler deployment current has a desired size 2

spec:
  replicas: 2

Only 1 user-scheduler pod can be active at a time.

1 user-scheduler pod acquires the leader-lock, and handles user requests for new hubs.
The other user-scheduler just waits.

I0723 23:54:51.705523       1 leaderelection.go:352] lock is held by user-scheduler-fc9c5b9bf-2chsl_184ca957-05ce-404b-867c-4ff2438352d4 and has not yet expired
I0723 23:54:51.705546       1 leaderelection.go:253] failed to acquire lease jupyterhub/user-scheduler-lock

This is a good pattern for highly available applications, but

  • I don't think the user-scheduler goes down frequently.
  • user-scheduelr doesnt take long to start up
  • the hub pod doesn't have a backup

So its not clear if this is offering any benefit at all.

@kabilar kabilar added this to the do-eks-phase2 milestone Jul 29, 2024
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

2 participants