-
Notifications
You must be signed in to change notification settings - Fork 82
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
Upgrade to Confluent.Kafka 1.5.2 #185
Comments
Thank you for sharing it, @amotl Absolutely, I'd like to upgrade it once it comes. I'd like to upgrade the code to adopt the recommended configuration for Azure. |
Dear Tsuyoshi, librdkafka 1.5.2 GA has just been released, see [1]. For making progress on that, we will probably have to wait for the bump propagating to confluent-kafka-dotnet and being available on NuGet [2]. With kind regards, [1] https://github.com/edenhill/librdkafka/releases/tag/v1.5.2 |
Thanks. It's a good new. Once it is released. I'll release this library with it. |
Thanks. @mhowlett is on it, see confluentinc/confluent-kafka-dotnet#1432. |
Confluent.Kafka 1.5.2 has been released, see https://www.nuget.org/packages/Confluent.Kafka/. Thanks a bunch, @mhowlett and @edenhill! |
It's a good news I'll include it |
Sounds good? #186 |
Thanks a again for considering to upgrade to 1.5.2! Closing this now. |
Dear @TsuyoshiUshio, @fbeltrao and @ryancrawcour,
as I see you have upgraded to Confluent.Kafka 1.4.3 within #151 the other day, I would like to humbly point out confluentinc/librdkafka#3109 to you.
Without using the Azure Kafka bindings yet, we and others tripped into different issues when connecting to Event Hubs with librdkafka <1.5.0 through its Python binding confluent-kafka-python when running within a Kubernetes environment on Azure.
Now, as I believe the same things might also apply to the Azure Kafka bindings, I wanted to give you a heads up on this.
Without any offense to you or the networking infrastructure within Azure, citing others:
After some issues revolving around that had been popping up on the Confluent's issue trackers, @edenhill was able to add some mitigations to librdkafka just recently.
Apart from upgrading to the most recent version of librdkafka, I would like to emphasize that it is probably also crucial to apply the recommended configuration settings for Kafka on Azure as outlined within confluentinc/librdkafka#3109 (comment).
After applying these measures to our systems, things have improved tremendously.
With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: