-
Notifications
You must be signed in to change notification settings - Fork 440
Kafka: Application maximum poll interval exceeded #893
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
Comments
@KonstantinCodes you're running a long running producer of some sort? What phprdkafka / librdkafka combination you're running? Overall, it is kind of related to #749 (not running EDIT: I've looked up the warning message and - as I was kinda expecting - that this message is coming from a change introduced for librdkafka 1.0. |
@Steveb-p yeah it's kind of interesting. I'm running a long running consumer, but the messages start popping up after 25 seconds. So from what I read, you just have to run I have tried configuring the enqueue transport this way, but for some reason it's not working. I debugged it but didn't come to an conclusion. So I built my own KafkaTransport for Symfony Messenger, and there it's working fine. So I'm really puzzled, how this is happening. Mind you, I'm specifying the exact same config values for both. I might push the code, just to provide a reference. |
Please do, but overall it should work the same. After all, it should be the same KafkaConsumer class. It should be something not really related to enqueue, but PhpRdKafka itself. Gotta do some digging 😄 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue should be solved by #947 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
My consumer
Is always producing these messages:
Do you have an idea, how to fix this?
The text was updated successfully, but these errors were encountered: