-
Notifications
You must be signed in to change notification settings - Fork 882
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
Segmentation fault happens when trying to commit a message after the max.poll.interval.ms passed without polling #1707
Comments
confirmed the problem not from anything regarding the processing output function, as reproduced the problem with time.sleep
logs
|
I am able to reproduce this issue. Output of the message Check valid usage in Consumer example
|
I think we shouldn't through SegFault in this case even though this is not the correct usage. |
Description
when trying to commit a message after not polling for anything more than the max.poll.interval.ms, I'm getting a non-recoverable segmentation fault that I can't handle in an exception handler, causing the python interpreter to exit
How to reproduce
in the section above, if processing_output_function(output) takes more than the max.poll.interval.ms, that particular loop with end correctly, commit the message, and then on the next one, I consume a message that says
, decoding this fails with " json.decoder.JSONDecodeError" exception, when going to finally commit the message, the logs says
"commiting message"
segmentation fault
and I don't reach the part about
"message has been commited"
I'm not sure if this is a working as intended situation, but it seems weird that it will stop my pthon execution and with no way to handle an exit exception
for now I increased the polling max time but can fetch logs later on if requested
Checklist
Please provide the following information:
{...}
: "enable.auto.commit": False, "auto.offset.reset": "earliest"The text was updated successfully, but these errors were encountered: