Avoid deadlocks using thread pool with context to run async futures#2475
Merged
MikeEdgar merged 1 commit intostreamshub:mainfrom Apr 11, 2026
Merged
Avoid deadlocks using thread pool with context to run async futures#2475MikeEdgar merged 1 commit intostreamshub:mainfrom
MikeEdgar merged 1 commit intostreamshub:mainfrom
Conversation
Signed-off-by: Michael Edgar <medgar@redhat.com>
|
jankalinic
approved these changes
Apr 11, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, when
CompletionStage*Async methods are invoked with the executor provided by aThreadContext, the thread that runs the task may be a Kafka Admin client thread. Additional use of the Admin client by another thread may result in a deadlock when there is a blocking task that is waiting for a result from the cluster.This PR adds a new
ContextualExecutorProviderthat instead runs the async tasks with the Quarkus executor thread pool, freeing the original thread to do additional work and avoiding a deadlock.