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

fix: Incorrect stored offset will be use after rebalanced #3782

Closed
wants to merge 2 commits into from

Conversation

intfish123
Copy link

Reset the stored offset in rebalanced, so that it will not commit previous stored offset to broker, (issue #3745, #3710).
And the codes in rdkafka_assignment.c -> rd_kafka_assignment_serve_removals() -> rd_kafka_offset_store0(rktp, RD_KAFKA_OFFSET_INVALID,RD_DONT_LOCK); can not fix the incorrect offset completely.

@intfish123
Copy link
Author

The base tag is v1.8.2, and I hope master can fix this problem quickly, because it happend daily on our production environment.

@edenhill
Copy link
Contributor

Thanks for your contribution!

We already have a fix for this issue in this PR: #3774

@edenhill
Copy link
Contributor

Can you try out the fix in PR #3774 and verify that it fixes the problem for your use-case?
Thanks

@intfish123
Copy link
Author

Can you try out the fix in PR #3774 and verify that it fixes the problem for your use-case? Thanks

ok, I will try it and verify on my test environment.
And branch resetrestored can be used with confidence on production environment?

@edenhill
Copy link
Contributor

The branch has been reviewed and tested, but it hasn't been released so there are no guarantees.
It would however be very valuable for everyone if it could be verified before merging,

@edenhill edenhill closed this Apr 5, 2022
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

Successfully merging this pull request may close these issues.

2 participants