-
Notifications
You must be signed in to change notification settings - Fork 811
Consumer group offset getting reset occationaly #410
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
Comments
I have the same issue with Rancher 2.0 and K8S. If I redeploy and keep 1 pod running until a new pod is available, Consumer will reset Offset. However, if I stop an old pod and start a new pod, it works fine. |
#424 |
Hi @rjshrjndrn and @anhtuanluu36. Thanks for reporting the issue. I just merged the fix contributed by @718529333 into |
Thank @718529333 and @stevevls. It works fine now. However, I have another issue: #426 |
@stevevls Sorry to bother u. But there is a problem trouble me. As when I use consumer group to cosume, I cannot use kafka-consumer-groups.sh to obtain the CURRENT-OFFSET any more. |
Hi,
Thank you for this awesome library.
I am facing a small Issue, where when I run this applicaiton for 2 different place( one at a time), occationaly I see the consumer group offset get reset. and reading starts from zero.
Eg: I've a container which runs of k8s, which will read and commit to the consumer group.
For debugging, I scaled that contiainer zero, and ran the application ( main.go) from my local, and it started to read from beginning. Any Ideas why is that.
The text was updated successfully, but these errors were encountered: