ipython / ipython/ipyparallel

kill engines by pid & client.shutdown blocks

Open
#229 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Jupyter Notebook
Stars
2.6k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

Hey @minrk and folks, in Issue #141 you recommend to use os.kill to interrupt engines by pid. I've been trying this approach, however, it seems that when engines are killed by pid you can no longer stop the ipcluster instance using `client.shutdown` without it blocking indefinitely. Is there a better way? I'd like to be able to interrupt all running jobs if, for example, a KeyboardInterrupt is raise, and then still be able to close the ipcluster instance remotely.

Here is an example where I run this first block of code followed by either of the following two code blocks:
```
import ipyparallel as ipp
import signal
import time
import os

## open client view
client = ipp.Client()

## get engines pids
engine_pids = client[:].apply(os.getpid).get_dict()
```

If I interrupt the engines then `shutdown` blocks indefinitely:
```
## submit a job to run for a while
for i in range(4):
async = client[i].apply(time.sleep, 30)

## interrupt each engine job before it finishes
for eng in engine_pids:
os.kill(engine_pids[eng], signal.SIGINT)

## kill the ipcluster instance
client.shutdown(hub=True, block=False)
```

Or if I just try `shutdown` without interrupting engines it doesn't block indefinitely, but it does still block for the full 30 seconds, whether or not I tell it `block=False`.
```
## submit a job to run for a while
for i in range(4):
async = client[i].apply(time.sleep, 30)

## soft shutdown
client.shutdown(hub=True, block=False)
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.