New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The upper limit of the thread pool size has probably been reached. #2021
Milestone
Comments
Can you please include the complete error stack trace (look in the .nextflow.log file) |
Sure, |
Adding here list of different thread pool implementation for reference default
sync
bound
unbound
|
@pditommaso do you need something from my side such as running more tests? |
I'll give a try asap. tx! |
pditommaso
added a commit
that referenced
this issue
Apr 18, 2021
Uploaded a patch on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Running the nf-core/sarek pipeline from a node with 128 Cores and 256 Threads, 1TB ram using Singularity and SGE.
Similar to #1871 and related to #92
This is the first time I am facing this issue. My team is running successfully from the same machine, other nf-core pipelines w/o reporting any problem.
go to the bottom for the solution.
Expected behavior and actual behavior
Run the nf-core/sarek pipeline; running the internal test of the pipelines was fine for all of them.
I got the pipeline interrupted and resumed several times when running on real data. Every time I resumed the pipieline another step got the thread pool size error.
Steps to reproduce the problem
The discriminant is a node with presumably an higher number of core/threads.
Program output
Environment
Additional context
Using
the pipeline run smoothly w/o issues.
The text was updated successfully, but these errors were encountered: