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: client has run out of available brokers #2891

Open
logic-building opened this issue May 7, 2024 · 3 comments
Open

Kafka: client has run out of available brokers #2891

logic-building opened this issue May 7, 2024 · 3 comments

Comments

@logic-building
Copy link

Problem Description: (Not issue with latest sarama and latest kafka)
I get the error:
Kafka: client has run out of available brokers.
Version:
with kafka version : 2.11-1.0.0 and
sarama version 1.43.2

and fix is 1.40.0 sarama version . Just wanted make note somewhere.

And I don't see this issue at all with latest kafka and latest sarama.
kafka: 2.13_3.2.3
sarama: 1.43.2

@puellanivis
Copy link
Contributor

puellanivis commented May 7, 2024

Wait, what? We recently ran into this, and we were using v1.42.1… what change could have resolved this?

@dnwe
Copy link
Collaborator

dnwe commented May 7, 2024

@puellanivis I'm not sure if its the same for you, but in @logic-building 's case I think this is just a scenario of not pinning an explicit KafkaVersion in the sarama.Config field.

In Kafka 1.40.x and older the default value if you didn't have a pinned kafka version was 1.0.0.0 protocol. In Sarama 1.41.x and newer we bumped the default to 2.1.0.0 protocol as per the Changelog https://github.com/IBM/sarama/releases/tag/v1.41.0 — this was at the request of the Kafka maintainers who are looking to remove support for older protocol versions.

That's why the problem was resolved both by rolling back client version (then rolling back to default 1.x.x.x protocol) or by rolling forward kafka version (because it then supported protocol 2.1.0.0 fine).

@puellanivis
Copy link
Contributor

I’ll keep an eye out. I think we only saw it the once. Also, I’m pretty sure we updated to the new version already as well.

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

3 participants