-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Seeing EOF/panic with v1.42.1 against MSK (Amazon) 2.4.1.1 that is not seen in v1.42.0 #2719
Comments
@JeffBNimble can you add logs from Sarama and/or Kafka to help show your problem? You can set Can you also double check and confirm that your apps sarama.Config has My assumption is that #2705 is causing the problem and your remote server doesn't understand the protocol version it is receiving, but if your sarama.Config version matches your remote cluster then it shouldn't be happening |
@JeffBNimble did you manage to resolve this issue? any update? |
Hello @dnwe. I'm incredibly sorry for the delay in responding. I saw your response a few weeks ago and have been at an AWS conference and then I'm on PTO through the end of the year. I will verify this in early January when I return and will reply. Thank you for checking back on this. |
No worries, enjoy the holidays and lets catch up in the New Year |
@JeffBNimble any more we can do here? |
We are good. The problem was what you said so good to close this out. Thank
you!
Thank you,
Jeff Roberts
…On Sun, Feb 11, 2024 at 8:16 AM Dominic Evans ***@***.***> wrote:
@JeffBNimble <https://github.com/JeffBNimble> any more we can do here?
—
Reply to this email directly, view it on GitHub
<#2719 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFS4LNEJOWKP5ULLE76CG3YTDHDPAVCNFSM6AAAAAA7FBQR3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXG43DOMJZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Cool, thanks Jeff |
Is anyone having trouble with the latest v1.42.1 release? I pulled it in and now my service panics with either a "broken pipe" error or an EOF error when attempting to consume. I reverted back to 1.42.0 and everything works fine.
Originally posted by @JeffBNimble in #2712 (comment)
My Kafka information:
Kafka version 2.4.1.1
Provider: MSK (Amazon)
Using SSL (Port 9094)
The text was updated successfully, but these errors were encountered: