2.x: Add interruptible mode to Schedulers.from #6370
Merged
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.
By default, the
Schedulers.fromuses a trampoline to ensure worker tasks are executed FIFO and non-overlappingly on any potentially multi-threadedExecutor. This old setup didn't allow task interruption due to this disconnect between the trampoline task and the operator task. (In contrast, the standard schedulers use single threaded executors and theirFutureis linked and interruptible when the operator task is cancelled).This PR add an interruptible mode to the
Schedulers.fromvia a paramerer in a new overload and some internal dispatching based on this mode selector. ExistingSchedulers.from(Executor)users should still behave the same.Resolves: #6368