We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I am using the following versions of the libraries.
kafka == 1.3.5 kafka-python == 2.0.1
We sometimes see that batches are expired in accumulator. But I have been observing that these messages are not retried by the producer.
I see that this behaviour has been updated in the apache kafka via https://issues.apache.org/jira/browse/KAFKA-5621 https://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer
Is this behavior present in the kafka-python library versions that we are using or is this behavior yet to be added ?
Also, in general why do batches expire or are not able to be sent even when there is no downtime on server? Is this a common issue ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I am using the following versions of the libraries.
kafka == 1.3.5
kafka-python == 2.0.1
We sometimes see that batches are expired in accumulator. But I have been observing that these messages are not retried by the producer.
I see that this behaviour has been updated in the apache kafka via
https://issues.apache.org/jira/browse/KAFKA-5621
https://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer
Is this behavior present in the kafka-python library versions that we are using or is this behavior yet to be added ?
Also, in general why do batches expire or are not able to be sent even when there is no downtime on server?
Is this a common issue ?
The text was updated successfully, but these errors were encountered: