-
Notifications
You must be signed in to change notification settings - Fork 801
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
Multiple consumer group offset problems with 0.4.36 #1021
Comments
+1, with the new version the consumer group lag increases |
I am suspecting this PR #947 |
Hi @dselans, Thanks for reporting these issues. Based on your Kafka version it looks like you're using MSK is that correct? If so are you able to reproduce your issues against non-MSK clusters? I'm struggling to reproduce this behavior, are you able to provide logs from your readers? They may be helpful in determining what's going on. https://pkg.go.dev/github.com/segmentio/kafka-go#readme-logging Thanks! |
I am facing partially the same issue and it caused a problem on our side during this week due to duplicates that were generated in large quantity offsets are committed partially If it helps I started receiving multiple warnings also after this upgrade
I agree on this aspect too as I see memberID being introduced in this PR but not entirely sure of the change
|
@rhansen2 yes, we're using MSK; we also observed similar issues + duplicates in GCP running in k8s ( kafka:2.8.0-debian-10-r43). I forgot to mention the dupe issue that @RO-29 posted about. We saw dupes and the offset issues in Kafka 2.8.0 but I assume that's because of the funky offset problems. I think we did not see the dupe issue in MSK but that might be because of insufficient testing. |
@rhansen2 We already moved off of 0.4.36 to .35 so I do not have a way to test it again right away. I can do it if you cannot replicate but it'll have to wait until tomorrow. LMK |
my config is likse what @dselans mentioned and on top i get errors like
kafka version: |
We had multiple issues with 0.4.36 as well:
Both issues were fixed with the downgrade to 0.4.35 |
#1022 Contains some potential fixes for some of the issues 0.4.36 but I'm still not able to reproduce any issues with committing offsets in MSK, Strimzi or running Kafka locally. Some of the issues seem related to interaction with other members of consumer groups. Is anyone using a mixture of clients within a single consumer group? As always, logs are very helpful for debugging. Thanks! |
Hello, I have the same problem here some logs, maybe they will help to localize the issue.
|
I have also tried the fix:
It works fine for me, here are some logs:
|
Hi @vitaly-m, I've merged that branch and released it as https://github.com/segmentio/kafka-go/releases/tag/v0.4.37 . Please let me know if it works for you or if you experience any other issues, thanks! |
v0.4.37 did not resolve this issue for my team. We upgraded our go dependencies and all kafka communication within our k8s cluster has since stopped working. After a lot of investigation we have determined we need to downgrade to v0.4.35 to fix the problem. I recommend v0.4.36 and v0.4.37 be reverted to bring the latest release back to a reliable working state while this issue is being worked out. |
Hi @mangoleaf Are you able to provide any information about the issues you're seeing or how to reproduce them? |
Consumer group changes have been reverted in https://github.com/segmentio/kafka-go/releases/tag/v0.4.38 |
Describe the bug
Several consumer group issues with
ReadMessage
andFetchMessage
when using lib version0.4.36
:CommitMessages
is called manually after a successfulFetchMessage
0.4.35
fixes both of the issuesKafka Version
2.4.1.1
To Reproduce
Thank you!
The text was updated successfully, but these errors were encountered: