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

kafka 2.0 support #440

Closed
golonzovsky opened this issue Aug 8, 2018 · 9 comments
Closed

kafka 2.0 support #440

golonzovsky opened this issue Aug 8, 2018 · 9 comments

Comments

@golonzovsky
Copy link

golonzovsky commented Aug 8, 2018

Currently Burrow reports growing lags for kafka 2.0 brokers, while kafka-consumer-groups reports zero lag.

Just to mention, from kafka 2.0 KIP-222 ConsumerGroup operations of AdminClient could be used to get groups and offsets..

@hejiaji
Copy link

hejiaji commented Aug 13, 2018

Any plan for support kafka 2.0?????

@lukaalex
Copy link

I think there is an issue with Kafka 2.0. I believe it is related to this library that burrow uses https://github.com/Shopify/sarama

@ericfgarcia
Copy link

Same question as hejiaji had above. We are looking to upgrade Kafka, but love burrow.

@sfrooster
Copy link

We just ran into this today after upgrading to 2.0....

@pikrzysztof
Copy link

Sarama supports kafka 2.0 as of release 1.18.0

https://github.com/Shopify/sarama/releases/tag/v1.18.0

@haeuserd
Copy link
Contributor

See #447

bai added a commit that referenced this issue Oct 2, 2018
Upgrade sarama to support Kafka 2.0.0 (#440)
@bai
Copy link
Collaborator

bai commented Oct 2, 2018

#447 was merged.

@bai bai closed this as completed Oct 2, 2018
@golonzovsky
Copy link
Author

@bai 👍
maybe not the best place to ask, but are there plans for releasing 1.2 any time soon? or its better to go with own build from master so far?

@gabrielfsousa
Copy link

i would luv kafka 2.0 support !!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants