This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
Unbounded ThreadPool is used for too many operations #2957
Assignees
Milestone
Comments
kolloch
pushed a commit
that referenced
this issue
Jan 12, 2016
for selected operations. And make it bounded ;)
kolloch
pushed a commit
that referenced
this issue
Jan 12, 2016
* use it only for blocking IO * make it use a fixed number of threads
kolloch
pushed a commit
that referenced
this issue
Jan 12, 2016
* use it only for blocking IO * make it use a fixed number of threads
kolloch
pushed a commit
that referenced
this issue
Jan 12, 2016
* use it only for blocking IO * make it use a fixed number of threads
gkleiman
added a commit
that referenced
this issue
Jan 13, 2016
…dpool Fixes #2957 - improve usage of io threadpool
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ThreadPoolContextprovides an unbounded cached ThreadPool namedcontext. The comment specifies that this should only be used for blocking IO operations but in reality this context is used for many operations.This can lead to
OutOfMemoryExceptions and other resource exhaustion problems.The text was updated successfully, but these errors were encountered: