kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Hauch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5704) Auto topic creation causes failure with older clusters
Date Fri, 04 Aug 2017 22:55:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115067#comment-16115067

Randall Hauch commented on KAFKA-5704:

The fix is straightforward: [this block|https://github.com/apache/kafka/blob/]
should log the appropriate message and return an empty set. Then, the initializer in [KafkaBaseLog|https://github.com/apache/kafka/blob/]
will complete by doing nothing, and the producer will get the topic metadata that will result
in the broker auto-creating the topic if missing and if so configured.

> Auto topic creation causes failure with older clusters
> ------------------------------------------------------
>                 Key: KAFKA-5704
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5704
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions:
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Randall Hauch
> The new automatic internal topic creation always tries to check the topic and create
it if missing. However, older brokers that we should still be compatible with don't support
some requests that are used. This results in an UnsupportedVersionException which some of
the TopicAdmin code notes that it can throw but then isn't caught in the initializers, causing
the entire process to fail.
> We should probably just catch it, log a message, and allow things to proceed hoping that
the user has already created the topics correctly (as we used to do).

This message was sent by Atlassian JIRA

View raw message