[
https://issues.apache.org/jira/browse/KAFKA-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231088#comment-14231088
]
Joel Koshy commented on KAFKA-1787:
-----------------------------------
Yeah that is one issue; [~onurkaraman] and I had discussed this offline a few
days ago. Another obvious issue is that it won't help with consumers that
happen to be down while the delete topic happens. Our conclusion was that
ultimately some kind of topic versioning in combination with a create-topic API
may be necessary.
So I think we can close this as out of scope for 0.8.2
> Consumer should delete offsets and release partition ownership for deleted
> topics
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-1787
> URL: https://issues.apache.org/jira/browse/KAFKA-1787
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2
> Reporter: Joel Koshy
> Assignee: Onur Karaman
> Priority: Blocker
> Fix For: 0.8.2
>
>
> Marking as a blocker for now, but we can evaluate.
> If a topic is deleted, the consumer currently does not rebalance
> (handleDataDeleted is a TODO in ZooKeeperConsumerConnector)
> As a result, it will continue owning that (deleted) partition and continue to
> issue fetch requests. Those fetch requests will result in an
> UnknownTopicOrPartition error and thus will result in TopicMetadataRequests
> issued by the leader finder thread which can recreate the topic if
> auto-create is turned on.
> Furthermore if we don't delete the offsets it is possible to lose messages if
> the topic is recreated immediately and the previously checkpointed offset
> (for the old data) is small. E.g., if a consumer is at offset 10 on some
> partition, and if the partition is deleted and recreated and 15 messages are
> sent to it then the first 10 messages will be lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
