You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2020/05/22 08:49:00 UTC

[jira] [Assigned] (KAFKA-10006) Streams should not attempt to create internal topics that may exist

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

Luke Chen reassigned KAFKA-10006:
---------------------------------

    Assignee: Luke Chen

> Streams should not attempt to create internal topics that may exist
> -------------------------------------------------------------------
>
>                 Key: KAFKA-10006
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10006
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Sophie Blee-Goldman
>            Assignee: Luke Chen
>            Priority: Major
>
> During assignment, Streams will attempt to validate all internal topics and their number of partitions, and create them if necessary. However we have seen that the InternalTopicManager will occasionally try to recreate internal topics that already exist when the broker is unavailable, and the describeTopics request fails. 
> This is because we catch both UnknownTopicOrPartitionException AND LeaderNotAvailableException and treat them the same, ie we assume the topic does not exist. We shouldn't try to create topics until we've validated that they don't actually exist. If we can't connect to the brokers to check whether the topic exists, there's no reason to believe we would be able to create the topic anyway.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)