You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 24, 2024. It is now read-only.
Describe the bug
Currently, KoP starts with a configed partition number for offset topic
If we changed the offsetsTopicNumPartitions in broker.conf or upgrade from a lower version which does not have the configuratioin for offsetsTopicNumPartitions, kop can not find the correct partition for a given consumer group.
To Reproduce
Steps to reproduce the behavior:
start kop, create a topic , then produce some messages and consumer part of theses messages
change the offsetsTopicNumPartitions in broker.conf and restart
continue consume the same topic with the same consumer group
may see data loss
Expected behavior
kop should keep compatibility when upgrade or change the configuration