Fix for "One or more background workers are no longer alive. Exiting" errors#136
Open
MikeUU332 wants to merge 1 commit intoMIC-DKFZ:masterfrom
Open
Fix for "One or more background workers are no longer alive. Exiting" errors#136MikeUU332 wants to merge 1 commit intoMIC-DKFZ:masterfrom
MikeUU332 wants to merge 1 commit intoMIC-DKFZ:masterfrom
Conversation
Added global mutex instead of threadpool_limits
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
See also MIC-DKFZ/nnUNet#2910, this is the same issue and fix.
Hello,
We encountered the "One or more background workers are no longer alive. Exiting" error as described in:
#134
#133
when running nnUNet on an HPC cluster. A colleague and I looked into this issue and came across this link:
joblib/threadpoolctl#176
which says that using with threadpool_limits is not thread safe and to use a global mutex instead. with threadpool_limits is used in both nnUNet and batchgenerators libraries. By using a global mutex instead of with threadpool limits as done in this pull request, we no longer encounter this issue. We verified that nnUNet output is similar (they can't be identical with the non-determinative multi-threaded launcher).
We encountered this error with both nnUNet and the batchgenerators library so a similar pull request was made in nnUNet.