Set default value of --max-tasks to None, which effectively makes pool workers work forever.
ClosedPublic
Actions

Authored by adomaitis on Aug 21 2019, 12:21 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Wed, Apr 17, 11:31 AM

	Unknown Object (File)
	Wed, Apr 10, 10:06 PM

	Unknown Object (File)
	Wed, Apr 10, 3:02 AM

	Unknown Object (File)
	Sun, Apr 7, 4:21 PM

	Unknown Object (File)
	Wed, Apr 3, 1:40 PM

	Unknown Object (File)
	Wed, Apr 3, 1:40 PM

	Unknown Object (File)
	Wed, Apr 3, 1:40 PM

	Unknown Object (File)
	Mon, Mar 25, 3:02 AM

View All 33 Files

Subscribers

machniak

petersen

Details

Reviewers

vanmeeuwen

Commits

rP00080f3bb1e2: Set default value of --max-tasks to None, which effectively makes pool workers…

Summary

That should be a workaround for issue when multiprocessing spawns a process which never gets a task and that ends up with all pool processes not getting into a state to accept new task and emails start congest. Most probably that is a deadlock situation described in https://codewithoutrules.com/2018/09/04/python-multiprocessing/ . The solution is in Python3.