search

jupyter / nb2kg

Other
73 stars 31 forks source link

restart jupyter server and restore kernel #11

Closed wangqiaoshi closed 6 years ago

wangqiaoshi commented 6 years ago

if i want to shutdown jupyter server and not kill running kernel ,How will the configuration. Waiting for your answer. thank you!

kevin-bates commented 6 years ago

@wangqiaoshi - could you please clarify your question?

Given you've posted this to NB2KG implies you're using Notebook with NB2KG on one server and targeting Jupyter Kernel or Enterprise Gateway via KG_URL on another. It sounds like you want to shutdown the Notebook server yet keep the kernel running and managed via JKG or JEG and would like to know how to do that - is that correct?

Given that a shutdown of the Notebook server will automatically issue shutdown requests for each of its managed kernels (regardless of whether NB2KG is installed or not) indicates leaving the kernels running is not the intention, nor am I aware of any way around this.

If this were supported, would you then want the ability to connect back to the kernel? And if so, do you expect to see all the output produced while disconnected?

Can you describe your use case?

wangqiaoshi commented 6 years ago

Thank you for your answer!

image

kevin-bates commented 6 years ago

@wangqiaoshi - thank you for the diagram.

We plan on adding this kind of functionality into Jupyter Enterprise Gateway which we refer to on our roadmap as session persistence. I'm fairly certain that such functionality doesn't exist in Jupyter Notebook, nor is it planned; same goes for Jupyter Kernel Gateway.

Some of this functionality exists in Jupyter Enterprise Gateway today, but is persisted only to a local file (which could be placed into a shared file system) and must be enabled by an undocumented configuration variable (--KernelSessionManager.enable_persistence=True). With that, you could start a kernel (on a remote node), kill the gateway server (either kill -9 <gateway_pid> or reboot the server), then restart another gateway server where the persistence file is available, and it will connect back up with any kernels. The client notebook user, needs to issue an explicit reconnect via the kernel tab to re-establish connectivity with the notebook cells.

I hope that helps.

kevin-bates commented 6 years ago

Closing issue due to lack of activity. Please re-open if necessary.