KAYAK-3387 Most Consumer operations are blocking and interruptible #835
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.
KAYAK-3387 These consumer operations are synchronous and blocking. The calling thread is blocked until results are returned. There may be some asynchronous I/O down underneath in the Java consumer, but we don't have access to it. These operations should thus be shifted to cats-effect's blocking context/thread pool, so that no threads in the compute pool are blocked.
This PR uses
interruptible
instead of justblocking
. There is evidence thatThread.interrupt
will actually interrupt/cancel the underlying operations.Also removed some unneeded trace/debug logging from the consumer.
Reference: CE3 thread model.