Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Explore possible compatibility issues between Notebook and Enterprise Gateway#1037

kevin-bates started this conversation inGeneral
Discussion options

This discussion item derives from a conversation started onjupyter/notebook#6251 inthis comment. I asked that the discussion and exploration of incompatibility between notebook and EG with respect to asynchronous kernel management be moved here for the time being since it is EG-specific.

cc:@Vishwajeet0510,@rahul26goyal

You must be logged in to vote

Replies: 1 comment

Comment options

kevin-bates
Feb 2, 2022
Maintainer Author

As per my understanding, from Jupyter Notebook v6.1.0 async kernel management is supported and corresponding changes on JEG side are supported from JEG v2.1.1 onwards.

Ah, ok. First, you should be using async kernel management as soon as possible. Its primary consumers are Jupyter applications that need to frequently spawn kernels - which is EG's exact intent. That said, I understand things can be slow to change at some companies (typically larger).

Async kernel management is optional. In fact, in the current Notebook server release, it'sstill using synchronous kernel management. Jupyter Server enables Async KM by default, but userscould go back to synchronous if they choose - although it's been fairly stable.

I think you should be able to run with EG 2.1.0 against the latest Notebook server - provided yourjupyter_client version remains < 7.0.

Are you seeing otherwise?

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
1 participant
@kevin-bates

[8]ページ先頭

©2009-2025 Movatter.jp