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

Consumer offsets migration did not finish after an upgrade #5008

Closed
mmaslankaprv opened this issue Jun 2, 2022 · 0 comments · Fixed by #4901
Closed

Consumer offsets migration did not finish after an upgrade #5008

mmaslankaprv opened this issue Jun 2, 2022 · 0 comments · Fixed by #4901

Comments

@mmaslankaprv
Copy link
Member

Problem description

During one of the cluster upgrade operations all consumers were not able to continue its operation. Consumers were 'stuck' and not being able to make progress.

Root cause of the problem was the fact that __consumer_offsets topic migration operation did not finish.

Consumer offsets migration is executed after all nodes in the cluster are updated and report that consumer_offsets feature is ready. For the time of migration we block all consumer groups operations. When migration is being executed all consumer group APIs will return NOT_COORDINATOR error. After all nodes finish migration all consumer groups state is available in new __consumer_offsets topic and all operations are being routed to it.

Problem analysis

One of the __consumer_offsets topic partition did not finish migrating preventing the whole migration step from finishing.
Following log entry was found in 2 out of 3 nodes:

INFO  2022-05-21 01:49:09,850 [shard 34] group-metadata-migration - group_metadata_migration.cc:377 - transforming data from {kafka_internal/group/24} to {kafka/__consumer_offsets/24} - is leader: false

This is expected behavior as on each node which host old kafka_internal/group topic replica a reconciliation loop is running checking if groups state recovered from migrated topic is exactly the same as the state of a groups when read from old kafka_internal/group topic.

Steps taken to investigate/fix the error:

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 a pull request may close this issue.

1 participant