[
https://issues.apache.org/jira/browse/KAFKA-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942160#comment-17942160
]
Andrew Schofield commented on KAFKA-19116:
------------------------------------------
The same problem occurs with deleting a share group. It looks like the
share-partition retains its previous fetch offset across these administrative
operations.
> Deletion of share group offsets does not reset the position as expected
> -----------------------------------------------------------------------
>
> Key: KAFKA-19116
> URL: https://issues.apache.org/jira/browse/KAFKA-19116
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 4.1.0
> Reporter: Andrew Schofield
> Assignee: Apoorv Mittal
> Priority: Major
> Fix For: 4.1.0
>
>
> Here are the steps to reproduce.
> # Create a topic T1 with a single partition.
> $ kafka-topics.sh --create --topic T1
> # Start the console producer and produce three records "one", "two", "three".
> Leave it running.
> # Start the console share consumer, and leave it running.
> $ kafka-console-share-consumer.sh --topic T1
> No records are consumed.
> # Send another record "four" using the console producer.
> # Record "four" is consumed by the console share consumer.
> # Describe the share group "console-share-consumer".
> $ kafka-share-groups.sh --describe --group console-share-consumer
> There should be an offset for topic T1, partition 0.
> # Stop the console share consumer so that the group is empty.
> # Delete the offset for topic T1, partition 0.
> $ kafka-share-groups.sh --delete-offsets --group console-share-consumer
> --topic T1
> # Describe the share group again to confirm the offset is shown as "-".
> # Send another record "five" using the console producer.
> # Restart the console share consumer. In theory, no records will be consumed
> because the fetch position should be re-initialized as the latest offset.
> Actually, record "five" is consumed.
> # Send another record "six" using the console producer.
> # The console share consumer should consume "six" and should not have
> consumed "five".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
