Allow to mark workers as fork unsafe #55
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When some part of an application is hard or impossible to make fork-safe, but rarely called, it's possible to simply mark the worker as fork unsafe, and rely on its siblings to fork the next generation.
In the eventually where all the workers end up marked fork unsafe, no new generation will be spawned, unless of course one of the unsafe workers die and is replaced by a fresh one.
So this is only meant as a workaround for infrequently called things.