在本文档(https://pymotw.com/3/concurrent.futures/)中,它指出:
ProcessPoolExecutor的工作方式与ThreadPoolExecutor相同,但使用进程而不是线程。这允许CPU密集型操作使用单独的CPU,而不会被CPython解释器的全局解释器锁阻止。”
听起来不错!它还说:
“如果某个工人进程发生意外导致其退出,则PrExsPoSQL执行程序被认为是“坏的”,不再调度任务。
这听起来很糟糕:(所以我想我的问题是:什么被认为是“出乎意料的”这是否意味着出口信号不是1?我能安全退出线程并仍然处理队列吗?示例如下:

from concurrent import futures
import os
import signal


with futures.ProcessPoolExecutor(max_workers=2) as ex:
    print('getting the pid for one worker')
    f1 = ex.submit(os.getpid)
    pid1 = f1.result()

    print('killing process {}'.format(pid1))
    os.kill(pid1, signal.SIGHUP)

    print('submitting another task')
    f2 = ex.submit(os.getpid)
    try:
        pid2 = f2.result()
    except futures.process.BrokenProcessPool as e:
        print('could not start new tasks: {}'.format(e))

最佳答案

我没有看到它IRL,但是从代码来看,返回的文件描述符似乎不包含结果队列文件描述符。
从concurrent.futures.process:

    reader = result_queue._reader

    while True:
        _add_call_item_to_queue(pending_work_items,
                                work_ids_queue,
                                call_queue)

        sentinels = [p.sentinel for p in processes.values()]
        assert sentinels
        ready = wait([reader] + sentinels)
        if reader in ready:  # <===================================== THIS
            result_item = reader.recv()
        else:
            # Mark the process pool broken so that submits fail right now.
            executor = executor_reference()
            if executor is not None:
                executor._broken = True
                executor._shutdown_thread = True
                executor = None
            # All futures in flight must be marked failed
            for work_id, work_item in pending_work_items.items():
                work_item.future.set_exception(
                    BrokenProcessPool(
                        "A process in the process pool was "
                        "terminated abruptly while the future was "
                        "running or pending."
                    ))
                # Delete references to object. See issue16284
                del work_item

wait函数取决于系统,但假设linux操作系统(atmultiprocessing.connection,删除了所有与超时相关的代码):
    def wait(object_list, timeout=None):
        '''
        Wait till an object in object_list is ready/readable.

        Returns list of those objects in object_list which are ready/readable.
        '''
        with _WaitSelector() as selector:
            for obj in object_list:
                selector.register(obj, selectors.EVENT_READ)

            while True:
                ready = selector.select(timeout)
                if ready:
                    return [key.fileobj for (key, events) in ready]
                else:
                    # some timeout code

09-05 00:30