[
https://issues.apache.org/jira/browse/KAFKA-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571604#comment-14571604
]
Jiangjie Qin commented on KAFKA-2246:
-------------------------------------
Created reviewboard https://reviews.apache.org/r/35023/diff/
against branch origin/trunk
> UnknownTopicOrPartitionException should be an instance of
> InvalidMetadataException
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-2246
> URL: https://issues.apache.org/jira/browse/KAFKA-2246
> Project: Kafka
> Issue Type: Bug
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Attachments: KAFKA-2246.patch
>
>
> In new producer, if a message send failed, we only refresh metadata when the
> exception is an instance of InvalidMetadataException.
> UnknownTopicOrPartitionException should be a sub class of it instead of just
> RetriableException. The scenario we saw is that when a topic get deleted from
> broker, UnkownTopicOrPartitionException will be thrown. Assuming auto topic
> creation is turned on, supposedly the producer will be able to produce with
> retries after the topic get recreated. But because
> UnknownTopicOrPartitionException is not an instance of
> InvalidMetadataException, producer will not refresh metadata and retries are
> exhausted.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
