You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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).
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
The text was updated successfully, but these errors were encountered: