Skip to content
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

Telegraf kafka_consumer does not work with Kafka 2.0 #4588

Closed
HristoMohamed opened this issue Aug 23, 2018 · 4 comments
Closed

Telegraf kafka_consumer does not work with Kafka 2.0 #4588

HristoMohamed opened this issue Aug 23, 2018 · 4 comments
Labels
area/kafka bug unexpected problem or unintended behavior
Milestone

Comments

@HristoMohamed
Copy link

HristoMohamed commented Aug 23, 2018

Hi,
Updating Apache Kafka to 2.0.0 causes problems with the current version of the sarama library.
2018-08-23T11:32:57Z E! Error in plugin [inputs.kafka_consumer]: Consumer Error: kafka: error while consuming telegraftopic/22: kafka: error decodin:wqg packet: CRC didn't match expected 0x0 got 0xe38a6876

They have already addressed this:
IBM/sarama#1149

Maybe an update in the sarama library version is in order?
I already compiled telegraf (545b59f) with the latest sarama (647feef69a1a7e0e23cccceeb786176bc4fcf5ea). I can see that telegraf works properly now.
I have only tried it against kafka 2.0.0.

System info:

Telegraf version: Telegraf v1.7.3 (git: release-1.7 4dc29d0)
Kafka version: 2.0.0
Scala Version (for Kafka) : 2.12

Steps to reproduce:

  1. Try to consume from a kafka 2.0.0 topic
  2. Fail with:
    2018-08-23T11:32:57Z E! Error in plugin [inputs.kafka_consumer]: Consumer Error: kafka: error while consuming telegraftopic/22: kafka: error decodin:wqg packet: CRC didn't match expected 0x0 got 0xe38a6876
@glinton glinton added bug unexpected problem or unintended behavior area/kafka labels Aug 23, 2018
@danielnelson
Copy link
Contributor

@HristoMohamed Would you be able to try Telegraf master and set the new version option to 1.1.0? I think this may allow using Kafka 2.0 with the current version, and I would feel more comfortable backporting the version option to Telegraf 1.7.x.

@HristoMohamed
Copy link
Author

Hey,
Yes I can test by later this week.

@dvenza
Copy link

dvenza commented Aug 31, 2018

I can confirm that the latest master, with the version option works with Kafka 2.0

@danielnelson danielnelson added this to the 1.8.0 milestone Aug 31, 2018
@danielnelson
Copy link
Contributor

Good news, thanks for checking this out @dvenza.

I think this will need to wait for 1.8 because of the changes to the sarama library version.

wingyplus added a commit to wingyplus/telegraf that referenced this issue Sep 11, 2018
wingyplus added a commit to wingyplus/telegraf that referenced this issue Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kafka bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

4 participants