Closed lianglinhuan closed 1 year ago
I don't know why this error is reported, can you ask a professional to answer it? Honored
hello, I have this problem too, did you solve it?
x3
same problem here
Hi ! I achieve it ! I was working with test containers and I was shutting down the kafka container before the test is over.
Now it works !
Thanks
Is there any recent progress on this issue? I have same problem here. {"C":"sarama/consumergroup.go:237","L":"warn","M":"sarama NewClient error: kafka: client has run out of available brokers to talk to: 3 errors occurred:\n\t EOF\n\t EOF\n\t* EOF\n","T":"2023-06-05T10:23:20.875Z"}
If I set SASL here, it is probably because the SASL certification has not passed
"client has run out of available brokers to talk to" is a common error if there is a misconfiguration in protocol Version or SASL / SSL etc., but it needs the full logger output to diagnose
I'm going to close this old issue as the original post didn't include that and people are stumbling upon this whilst search for their own problem, but it would be better to raise a separate issue so that we can diagnose each case individually
Hello everyone, this is how I solved this problem: for reference only: I downgraded sarama to v1.19.0. The code is as follows: go get github.com/Shopify/sarama@v1.19.0 It will work normally
Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Configuration
What configuration values are you using for Sarama and Kafka?
Logs
When filing an issue please provide logs from Sarama and Kafka if at all possible. You can set
sarama.Logger
to alog.Logger
to capture Sarama debug output.logs: CLICK ME
``` ```
Problem Description