[
https://issues.apache.org/jira/browse/KAFKA-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vahid Hashemian updated KAFKA-4095:
-----------------------------------
Status: Patch Available (was: Open)
> When a topic is deleted and then created with the same name, 'committed'
> offsets are not reset
> ----------------------------------------------------------------------------------------------
>
> Key: KAFKA-4095
> URL: https://issues.apache.org/jira/browse/KAFKA-4095
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.10.0.0, 0.9.0.1
> Reporter: Alex Glikson
> Assignee: Vahid Hashemian
>
> I encountered a very strange behavior of Kafka, which seems to be a bug.
> After deleting a topic and re-creating it with the same name, I produced
> certain amount of new messages, and then opened a consumer with the same ID
> that I used before re-creating the topic (with auto.commit=false,
> auto.offset.reset=earliest). While the latest offsets seemed up to date, the
> *committed* offset (returned by committed() method) was an *old* offset, from
> the time before the topic has been deleted and created.
> I would have assumed that when a topic is deleted, all the associated
> topic-partitions and consumer groups are recycled too.
> I am using the Java client version 0.9, with Kafka server 0.10.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
