You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Joel Koshy (JIRA)" <ji...@apache.org> on 2014/12/02 08:06:12 UTC

[jira] [Resolved] (KAFKA-1787) Consumer should delete offsets and release partition ownership for deleted topics

     [ https://issues.apache.org/jira/browse/KAFKA-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Koshy resolved KAFKA-1787.
-------------------------------
    Resolution: Won't Fix

> 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)