-
Notifications
You must be signed in to change notification settings - Fork 237
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
group corodinate offset commit failure with same offsets #353
Comments
Depends on how many of those you have. If you use autocommit and next commit was successful it will have no impact. Probably the issue was in a connection loss, as long as those don't repeat frequently you should be ok.
Yes, it is an error, sorry about that. I will look into the log levels. Probably this case should not produce an error. |
Checked with Java client. The error is logged in the same |
My first question is should I be worried about this error since it is a
error
?The second thing is that I notice that all the topic offset are the same, which seems odd. Looking at the code, it seem to be a reporting error: https://github.com/aio-libs/aiokafka/blob/v0.4.0/aiokafka/consumer/group_coordinator.py#L930-L933, with the last
offset
was assigned here: https://github.com/aio-libs/aiokafka/blob/v0.4.0/aiokafka/consumer/group_coordinator.py#L850.The offset might also be reported incorrectly here.
https://github.com/aio-libs/aiokafka/blob/v0.4.0/aiokafka/consumer/group_coordinator.py#L876-L880
The text was updated successfully, but these errors were encountered: