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

Fix worker node servers getting killed after JuptyerHub restart #124

Merged
merged 1 commit into from
Apr 11, 2022

Conversation

ericdwang
Copy link
Contributor

Follow-up to #106 and fixes #104 (again)

We discovered in the JupyterHub logs that it was trying to contact the
master node for jobs scheduled on worker nodes which was incorrect and
led to them getting killed:

Notebook server job 157 started at hpc-worker-02:52649
(JupyterHub restart)
server never showed up at http://hpc-master-node:52649

This fixes the problem by preserving self.server.ip similar to
self.server.port in QHubHPCSpawnerBase.poll().

Follow-up to nebari-dev#106 and fixes nebari-dev#104 (again)

We discovered in the JupyterHub logs that it was trying to contact the
master node for jobs scheduled on worker nodes which was incorrect and
led to them getting killed:

```
Notebook server job 157 started at hpc-worker-02:52649
(JupyterHub restart)
server never showed up at http://hpc-master-node:52649
```

This fixes the problem by preserving `self.server.ip` similar to
`self.server.port` in `QHubHPCSpawnerBase.poll()`.
@costrouc
Copy link
Member

Thanks @ericdwang!

@costrouc costrouc merged commit 4c66c58 into nebari-dev:main Apr 11, 2022
@ericdwang ericdwang deleted the fix-worker-node-killed-servers branch April 12, 2022 03:26
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.

JupyterLab servers are being killed when jupyterhub is updated
2 participants