Close and Halt does not stop instance... is it supposed to?

Responded

Follow

James Wilson

February 10, 2022 15:17

See title.

0

• Official comment

  

  Sarath Botlagunta February 10, 2022 16:03

  Same runtime instance could be in use by some other notebook.
  So just closing your notebook will not stop the instance automatically. As each runtime instance will have total time and idle time configured, they will be stopped once any of these times are hit.

  Comment actions Permalink
• 

  James Wilson February 10, 2022 16:04

  Okay so why does the button exist? It doesn't seem to do anything.

  0

  Comment actions Permalink
• 

  Sarath Botlagunta February 10, 2022 16:05

  Which button are you talking about?

  0

  Comment actions Permalink
• 

  Shahdy Ali Hassan February 10, 2022 16:24 (Edited February 10, 2022 16:47)

  Sarath Botlagunta, the question is asking about the Close and Halt option from the File menu within the Jupyter Hub menus:

  

  0

  Comment actions Permalink
• 

  Sarath Botlagunta February 10, 2022 17:22

  Close and Halt is for stopping the current executing cell and stopping the kernel.

  Kernel and runtime instance are two different things.

  Kernel is the main execution engine of the notebook. Any code that is written in a cell first goes to the kernel.

  Now kernel will decide if I can execute this code or do I need to forward this code further down.

  So if runtime is not attached, kernel is the only executor for your code.

  If runtime is attached and you include spark code in the cell (with %%spark magic), then kernel will redirect the code spark runtime and just start acting as a proxy in between.

   

  0

  Comment actions Permalink

Please sign in to leave a comment.