Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why use of Scheduler if the processing has been proven NON blocking please? #543

Open
patpatpat123 opened this issue Jan 30, 2023 · 0 comments

Comments

@patpatpat123
Copy link

Hello,

This is my first ticket in this project.

I would like to start with a big thanks. The talk in Kafka submit was very clear, easy to follow.

I am observing an issue for the reactive parallel consumer please:

https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-reactor/src/main/java/io/confluent/parallelconsumer/reactor/ReactorProcessor.java#L104

May I ask why the publication on the Scheduler please?

Let's suppose the processing of the event is NON blocking, not blocking at all (BlockHound tested non blocking etc...)

Should the Scheduler be removed, if the processing of the event itself has been assured NON blocking, and still be able to have the parallel reactive consumer?

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant