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

Seeing EOF/panic with v1.42.1 against MSK (Amazon) 2.4.1.1 that is not seen in v1.42.0 #2719

Closed
JeffBNimble opened this issue Nov 9, 2023 · 7 comments

Comments

@JeffBNimble
Copy link

JeffBNimble commented Nov 9, 2023

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)

@dnwe
Copy link
Collaborator

dnwe commented Nov 10, 2023

@JeffBNimble can you add logs from Sarama and/or Kafka to help show your problem? You can set sarama.Logger to a log.Logger to capture Sarama debug output.

Can you also double check and confirm that your apps sarama.Config has sarama.Config{Version: sarama.V2_4_1_1} or lower set?

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

@dnwe dnwe changed the title 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. Seeing EOF/panic with v1.42.1 against MSK (Amazon) 2.4.1.1 that is not seen in v1.42.0 Nov 10, 2023
@dnwe
Copy link
Collaborator

dnwe commented Dec 20, 2023

@JeffBNimble did you manage to resolve this issue? any update?

@JeffBNimble
Copy link
Author

@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.

@dnwe
Copy link
Collaborator

dnwe commented Dec 20, 2023

No worries, enjoy the holidays and lets catch up in the New Year

@dnwe
Copy link
Collaborator

dnwe commented Feb 11, 2024

@JeffBNimble any more we can do here?

@JeffBNimble
Copy link
Author

JeffBNimble commented Feb 11, 2024 via email

@dnwe
Copy link
Collaborator

dnwe commented Feb 11, 2024

Cool, thanks Jeff

@dnwe dnwe closed this as completed Feb 11, 2024
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

2 participants