-
Notifications
You must be signed in to change notification settings - Fork 32
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
Make it possible to restart JupyterHub with minimal service interruption #17
Comments
@jhamrick No updates on this one? Are you aware of similar efforts within JupyterHub ecosystem? |
In JupyterHub itself I believe it is now possible to restart the hub without restarting the proxy or any of the singleuser servers, though I haven't personally tested how this interacts with interruptions to service. You might try posting on the JupyterHub repo to get clarification on that. |
Thank you for a blazingly fast reply! :-) One more question, if you don't mind. I'm looking for an advice on using LDAP Authenticator Plugin for JupyterHub. Do you have experience in this area or can recommend someone who might help? |
Sorry, I don't have any experience with the LDAP plugin. I know there are lots of people who do who are on the Jupyter mailing list, though, so I'd recommend asking there. |
No problem. Will try to use the mailing list. Thank you! |
This would include starting the configurable-http-proxy separately from JupyterHub, which means JupyterHub could be restarted without interrupting users who are currently using the system (though it would prevent users from logging in during the restart).
This also includes creating an ansible tag or something that makes it easy to just perform the tasks necessary for restarting JupyterHub.
The text was updated successfully, but these errors were encountered: