-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Ingester not consuming messages with kafka server 2.x #1247
Comments
I owe you big time! downgrade kafka version, messages finally got processed. |
@jaegertracing/jaeger-maintainers sounds like this is closed by #1248 |
Still reproducible in 1.13.1. I'm using docker-compose & fast-data-dev
|
@klass-ivan You might be interested in #1640 ingester uses depracated sarama-cluster package, that sets kafka version to 0.9, this patch allows to override this setting with app settings. It is merged to master, but not released yet |
@marqc nevermind, the problem was in kafka advertised host incorrect for in-docker network. Thanks |
Requirement - what kind of business use case are you trying to solve?
Use recent kafka server with jaeger-collector and jaeger-ingester.
Specifically Kafka 2.0.1 with log.message.format.version=2.0-IV1
Problem - what in Jaeger blocks you from solving the requirement?
Jaeger depends on Shopify/Sarama:1.16 which does not support recent versions of kafka servers and message formats. With above kafka server config it does not consume messages. No errors/warnings is printed to log.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Update Shopify/Sarama dependency to latest stable version (1.20). https://github.com/Shopify/sarama/releases
Any open questions to address
The text was updated successfully, but these errors were encountered: