-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
Consumer can process only messages from one topic at a time #1688
Comments
I think you can leverage |
Yes, I have tried using It is understandable that new messages in Topic A should wait until the current batch is processed to maintain order, as required by Kafka. However, there is no reason why the consumer should not process messages from different topics concurrently. Each topic should be processed independently to ensure efficient message consumption. |
Oh, I missunderstood it, I was thinking about partitions in the same topic |
When consuming messages from topic A, the consumer gets blocked and does not pull messages from topic B until it has finished processing the messages from topic A.
Reproduction Steps and Original Issue:
This behavior can be reproduced and has been originally reported in the NestJS repository. For more details, you can refer to the issue and related comments here.
The text was updated successfully, but these errors were encountered: