-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Kafka consumer not reading any message with zero timeout_ms poll value #2609
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
@dpkp Thank you so much for your support, unfortunately it does not seem to solve the 0 timeout_ms issue since I put a record in the queue at 08:35 but it was never read until I changed the timeout_ms from 0 to 100 at 08:38.
|
Release 2.2.6 - The issue is still present but it keeps working fine with 100ms timeout (drawback of unnecessary cpu consumption in my environment). |
Once started the consumers and calling poll() with timeout_ms=0 (and facing the issue of not reading any message), changing the timeout_ms to 100 solves the issue since it starts reading messages on the next calls to poll() ... and apparently it keeps reading also after reverting the parameter back to 0. Could not grab the debug logging yet but if this can help I'll try to reproduce it with corresponding logs in the next days. |
timeout_ms=0 should work, but you will need to call it many times before all of the connection + group setup is completed and messages start flowing. |
Zero timeout_ms poll value is working fine with 2.0.2 and 2.0.6 but not any longer with latest releases (2.1.x, 2.2.x).
Using a non zero value solves the issue but in my very specific environment (HPE NonStop) using a non zero timeout_ms poll value leads to a quite higher cpu consumption, experienced years ago with 2.0.2 and also checked after running for a while with 2.2.3 .
The text was updated successfully, but these errors were encountered: