ipython / ipython/ipyparallel

kill engines by pid & client.shutdown blocks

未关闭
#229 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
bug
主要语言
Jupyter Notebook
星标
2.6k
派生
1k
PR 合并指标
30 天内没有已合并 PR

描述

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)
```

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。