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
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Sarama
Kafka
Go
Version 1.26.4 (2020-05-19)
0.10.1
1.14
Configuration
What configuration values are you using for Sarama and Kafka?
default config
Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.
logs: CLICK ME
Problem Description
When client gets metadata failed in multiple goroutines, client will retry get metadata in each goroutines after Metadata.Retry.Backoff, and each goroutine does not know other goroutines are sending metadata request
The text was updated successfully, but these errors were encountered:
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the master branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.
ghost
added
the
stale
Issues and pull requests without any recent activity
label
Mar 16, 2021
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 debugoutput.
logs: CLICK ME
Problem Description
When client gets metadata failed in multiple goroutines, client will retry get metadata in each goroutines after Metadata.Retry.Backoff, and each goroutine does not know other goroutines are sending metadata request
The text was updated successfully, but these errors were encountered: