Fix ThreadPool creation #261
Merged
Conversation
This file contains 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
Executors.defaultThreadFactory is creating a new ThreadFactory for each new thread created, messing up thread names and pool belongings. Now, we are passing a pool name when building a new executor service, and handling counter for threads belonging to this thread pool
tylerbenson
reviewed
Feb 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Executors.defaultThreadFactory()is creating a newThreadFactoryfor each new thread created, messing up thread names and pool belongings.Now, we are passing a pool name when building a new executor service, and handling counter for
threads belonging to this thread pool
Thread names before:
pool-2-thread-1
pool-3-thread-1
pool-4-thread-1
pool-5-thread-1
Thread names after:
jmxfetch-collectionPool-1
jmxfetch-collectionPool-2
jmxfetch-collectionPool-3
jmxfetch-recoveryPool-1