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

[Gateway] Track only this server's kernels #407

Merged
merged 1 commit into from
Feb 18, 2021

Conversation

kevin-bates
Copy link
Member

While working on Enterprise Gateway, I found that if a gateway server is hosting kernels from multiple lab servers (via either jupyter_server or notebook), all kernels managed by the gateway server could be shut down when terminating one of the lab servers. This change ensures that kernel-based operations of a given lab/notebook server only operate against its own kernels.

Also:

  • Updated log statements to f-strings in the working file.
  • Found the KernelHandlers get method hadn't transitioned to async def so I made that change.

Copy link
Contributor

@blink1073 blink1073 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@Zsailer Zsailer merged commit b5cebd6 into jupyter-server:master Feb 18, 2021
Zsailer added a commit to Zsailer/jupyter_server that referenced this pull request Nov 18, 2022
… calls (jupyter-server#407)

* hubble metrics to measure execution count and latency and all notebook service calls

* Bump to 0.21.1

* add metric for a disconnected kernel
hMED22 pushed a commit to hMED22/jupyter_server that referenced this pull request Jan 23, 2023
…ernels

[Gateway] Track only this server's kernels
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.

5 participants