You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@toree.apache.org by "Sanjay Saxena (JIRA)" <ji...@apache.org> on 2017/11/10 18:08:00 UTC
[jira] [Created] (TOREE-455) Toree should broadcast current status
when a client reconnects
Sanjay Saxena created TOREE-455:
-----------------------------------
Summary: Toree should broadcast current status when a client reconnects
Key: TOREE-455
URL: https://issues.apache.org/jira/browse/TOREE-455
Project: TOREE
Issue Type: Bug
Reporter: Sanjay Saxena
If the user starts new job in Apache Toree kernel and reconnects to the same kernel from a Jupyter Notebook, the Notebook client will not receive `Busy` kernel status. So, the user will not know that the kernel is in `Busy` state.
Note that a user can reconnect using Notebook UI `Kernel -> Reconnect` when the kernel is busy. At that time, the Notebook is reconnected to the kernel but shown as `Ready` (even if the code continues executing). The same behavior could be seen when the Notebook Server is installed remotely and there is network reconnect or if the user refreshes the Notebook in the browser when the kernel is in `Busy` state.
Implementing a workaround in the Notebook using the kernel_info request did not work as Toree sends the kernel_info response immediately even if the kernel is busy. And, Notebook interprets it as though Kernel is in `Idle` state by marking it as such in the metadata and the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)