3.x: Add fair mode overload to Schedulers.from(Executor) #6744
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.
The default
Schedulers.from
implementation uses an eager approach to execute tasks on the underlyingExecutor
which can lead to excessive thread occupation on its own, even if operators use buffering/prefetch of 1.This PR introduces a new overload with a fairness option so that tasks are submitted to the
Executor
in a non-overlapping and FIFO manner one by one.In addition, the scheduler retention tests have been cleaned up and reworked to not wait unnecessarily long for the GC to finish.
Related: #6696, #6697