-
Notifications
You must be signed in to change notification settings - Fork 649
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
Fail fast on librdkafka connection error #48
Comments
Connection errors are treated as temporary errors and librdkafka will retry connecting to its known brokers indefinately. Instead you should try to define your application-specific constraints in time:
And let the underlying client operate without interruption within those bounds, abstracting your application from Kafka specific know-how. Anyway, if you're not buying into this, or maybe just curious, you can look for the kafka.Error event. |
Thanks for the detailed explanation, that's a good way to treat these errors. |
@mcandre What if the broker is not down but the client is unable to connect due to a misconfiguration of the broker address. Unless we get a failure event it's not possible for us to know about the problem. |
|
When a Kafka connection fails in librdkafka, this information should propagate up to confluent-kafka-go, so that applications can decide to fail fast, reconnect, etc.
Right now, librdkafka reports connection errors to the console, but the confluent-kafka-go application continues as if everything is just fine.
The text was updated successfully, but these errors were encountered: