see #1804 Enforce 100K task cap on Schedulers.boundedElastic() #1900
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.
Another late change, but if we introduce the
boundedElastic()
singleton version of the scheduler, we might as well make it truly bounded, including in the number of task submissions it can "absorb" during a spike. Used to be unbounded, now bounded to 100K tasks.This is also more likely to uncover problematic scheduling of blocking tasks. Users switching from
elastic()
toboundedElastic()
and seeingRejectedExecutionException
s should challenge why their Reactor app schedules so many blocking tasks, and if still legitimate and necessary, use anewBoundedElastic
instance that is better tuned to their workload.