Message 154573 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	neologix, paul.moore, pitrou
Date	2012-02-28.21:42:12
SpamBayes Score	6.3557827e-06
Marked as misclassified	No
Message-id	<1330465333.6.0.44696664452.issue14148@psf.upfronthosting.co.za>
In-reply-to

Content
The problem is that queues and other synchronization objects can end up in an inconsistent state when a worker crashes, hangs or gets killed. That's why, in concurrent.futures, a crashed worker makes the ProcessPoolExecutor become "broken". A similar thing should be done for multiprocessing.Pool but it's a more complex object.

The problem is that queues and other synchronization objects can end up in an inconsistent state when a worker crashes, hangs or gets killed.
That's why, in concurrent.futures, a crashed worker makes the ProcessPoolExecutor become "broken". A similar thing should be done for multiprocessing.Pool but it's a more complex object.

History
Date	User	Action	Args
2012-02-28 21:42:13	pitrou	set	recipients: + pitrou, paul.moore, neologix
2012-02-28 21:42:13	pitrou	set	messageid: <1330465333.6.0.44696664452.issue14148@psf.upfronthosting.co.za>
2012-02-28 21:42:13	pitrou	link	issue14148 messages
2012-02-28 21:42:12	pitrou	create