[jira] [Commented] (TOREE-33) Ctrl-C not killing kernels
[
https://issues.apache.org/jira/browse/TOREE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157993#comment-16157993
]
Christian Kadner commented on TOREE-33:
---
The GitHub link from [~chipsenkbeil] no longer works, here's the updated link:
https://github.com/apache/incubator-toree/blob/master/kernel/src/main/scala/org/apache/toree/boot/layer/HookInitialization.scala#L67
{code}
import sun.misc.{Signal, SignalHandler}
// TODO: Signals are not a good way to handle this since JVM only has the
// proprietary sun API that is not necessarily available on all platforms
Signal.handle(new Signal("INT"), new SignalHandler() {
// ...
{code}
> Ctrl-C not killing kernels
> --
>
> Key: TOREE-33
> URL: https://issues.apache.org/jira/browse/TOREE-33
> Project: TOREE
> Issue Type: Bug
>Reporter: Chris Marcocci
>
> If the way to kill the kernel is now {{ctrl-z && kill %1}} that's fine, but
> the behavior should be consistent.
> For instance if the kernel is started with the notebook 2x {{ctrl-c}} will
> successfully stop the notebook server and the kernel it started, but if the
> kernel is started by itself 2x {{ctrl-c}} will not work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TOREE-437) Cell interrupts do not occur in background
[ https://issues.apache.org/jira/browse/TOREE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Bates updated TOREE-437: -- Description: Whenever Toree is run in the background - either directly from the shell or indirectly from the Jupyter stack that is started in the background - cell interrupts (via ctrl-C or SIGINT from parent) are not received - resulting in the inability to interrupt long-running cells. This can be most simply demonstrated by invoking run.sh into the background (e.g., run.sh &) then issue ctrl-C (or `kill -2 `) to no avail. This is related to TOREE-33 but only pertains to cell interrupt functionality since complete life-cycle management is assumed by the parent for the shutdown (double ctrl-C) scenario. was: Whenever Toree is run in the background - either directly from the shell or indirectly from the Jupyter stack that is started in the background - cell interrupts (via ctrl-C or SIGINT from parent) are not received - resulting in the inability to interrupt long-running cells. This can be most simply demonstrated by invoking run.sh into the background (e.g., run.sh &) then issue ctrl-C (or `kill -2 `) to no avail. This is related to [TOREE-33] but only pertains to cell interrupt functionality since complete life-cycle management is assumed by the parent for the shutdown (double ctrl-C) scenario. > Cell interrupts do not occur in background > -- > > Key: TOREE-437 > URL: https://issues.apache.org/jira/browse/TOREE-437 > Project: TOREE > Issue Type: Improvement > Components: Kernel >Affects Versions: 0.2.0 >Reporter: Kevin Bates >Assignee: Kevin Bates > Labels: usability > > Whenever Toree is run in the background - either directly from the shell or > indirectly from the Jupyter stack that is started in the background - cell > interrupts (via ctrl-C or SIGINT from parent) are not received - resulting in > the inability to interrupt long-running cells. > This can be most simply demonstrated by invoking run.sh into the background > (e.g., run.sh &) then issue ctrl-C (or `kill -2 `) to no avail. > This is related to TOREE-33 but only pertains to cell interrupt functionality > since complete life-cycle management is assumed by the parent for the > shutdown (double ctrl-C) scenario. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TOREE-437) Cell interrupts do not occur in background
Kevin Bates created TOREE-437: - Summary: Cell interrupts do not occur in background Key: TOREE-437 URL: https://issues.apache.org/jira/browse/TOREE-437 Project: TOREE Issue Type: Improvement Components: Kernel Affects Versions: 0.2.0 Reporter: Kevin Bates Assignee: Kevin Bates Whenever Toree is run in the background - either directly from the shell or indirectly from the Jupyter stack that is started in the background - cell interrupts (via ctrl-C or SIGINT from parent) are not received - resulting in the inability to interrupt long-running cells. This can be most simply demonstrated by invoking run.sh into the background (e.g., run.sh &) then issue ctrl-C (or `kill -2 `) to no avail. This is related to [TOREE-33] but only pertains to cell interrupt functionality since complete life-cycle management is assumed by the parent for the shutdown (double ctrl-C) scenario. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TOREE-299) Create spark context lazily to avoid long startup times for the kernel
[ https://issues.apache.org/jira/browse/TOREE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende resolved TOREE-299. --- Resolution: Duplicate Fix Version/s: 0.2.0 > Create spark context lazily to avoid long startup times for the kernel > -- > > Key: TOREE-299 > URL: https://issues.apache.org/jira/browse/TOREE-299 > Project: TOREE > Issue Type: Improvement >Reporter: Gino Bustelo > Fix For: 0.2.0 > > > Currently the options are to start or not start a kernel at startup time. The > "not start" option leaves it all to the user. > I propose that when the kernel is managing the spark context, that is starts > it lazily when the user first tries to get a hold of the reference. > I tried to do this as part of > https://github.com/apache/incubator-toree/pull/15 but hit some roadblocks > that I did not want to tackle as part of that PR. > Now that the `sc`is a `def` it can easily be made lazy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
