improve: caching executor for startup tasks and remove parallel()
#1755
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.
Using CachedThreadPool for startup tasks, this includes the controller and event source. And removing
parallel()
usage, that likely caused the rare deadlock in some operators.CachedThreadPool is ideal for such tasks, since it reuses and dynamically adjusts thread count. What we need is a separate thread on startup for each informer / event source. Also those threads are later autoamitcally removed, when not used anymore.