-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Output to Kafka does not recover after a Kafka node goes down #1113
Comments
Obviously has something to do with the required_acks setting, if that config is missing, what is the default value used? This is how my config looks now and everything works
|
it would use |
That makes sense that it would fail when the broker it is connected to fails, but why does it not recover when the broker comes back up? |
oh, I think I see the issue, when you don't specify I can change that by having the kafka producer have a more reasonable default, such as 3. |
3x Centos kafka/zookeeper cluster
1x Windows machine to run Telegraf
1x Centos Influxdb
On the Windows machine I have two instances of Telegraf running, one to gather metrics and write to Kafka and another to read from Kafka and write to Influxdb.
When I'm testing shutting down the kafka nodes to see how Telegraf handles it. Shutting down the Zookeper service that the Kafka consumer is using works fine, it automatically tries the next Zookeper node and continues.
On the other hand the Kafka output that is connected to the Kafka brokers fails completely when I shut down the Kafka service on the first node and continues to fail even after the service is up and running again.
The only way to get it working again is to restart the Telegraf process.
This is my output config
The text was updated successfully, but these errors were encountered: