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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Lets give it some time as few times some bugs were reported right after the releases.
Plan:
The text was updated successfully, but these errors were encountered:
Hello!
Appreciate the caution, in my organization we were bitten by consumption issues in librdkafka 2.1.0.
Will offer though that Confluent is recommending 2.3.0 in reaction to this issue: OffsetForLeaderEpoch loop of failed requests with multiple leader changes
The symptom of this bug is that a consumer will stop reading a rebalanced partition, indefinitely, even if no other consumer picks it up.
Sorry, something went wrong.
@samsm hey. Thank you for your insights. karafka-rdkafka already got 2.3.0 approved (ref karafka#43) and all integrations in karafka pass with 2.3.0.
I will release 0.14 with 2.2.0 and will then release 0.15 with backport later.
Thanks! Appreciate it
mensfeld
Successfully merging a pull request may close this issue.
Lets give it some time as few times some bugs were reported right after the releases.
Plan:
The text was updated successfully, but these errors were encountered: