[issue14148] Option to kill "stuck" workers in a multiprocessing pool

[Paul Moore]

Paul Moore <p.f.moore at gmail.com> added the comment:

As an alternative, maybe leave the "stuck" worker, but allow the pool
to recognise when a worker has not processed new messages for a long
period and spawn an extra worker to replace it. That would avoid the
starvation issue, and the stuck workers would die when the pool is
terminated.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14148>
_______________________________________