You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chris Egerton (Jira)" <ji...@apache.org> on 2019/10/16 19:51:00 UTC
[jira] [Commented] (KAFKA-8875) CreateTopic API should check topic
existence before replication factor
[ https://issues.apache.org/jira/browse/KAFKA-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953141#comment-16953141 ]
Chris Egerton commented on KAFKA-8875:
--------------------------------------
[~hachikuji] are there plans to backport this fix any further back than 2.3? This currently affects Connect since workers try to create their internal topics on startup, and users are forced to manually reconfigure the replication factors for those topics in their worker files even if the topics already exist if the replicator factors are greater than the number of available brokers in the Kafka cluster.
> CreateTopic API should check topic existence before replication factor
> ----------------------------------------------------------------------
>
> Key: KAFKA-8875
> URL: https://issues.apache.org/jira/browse/KAFKA-8875
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: huxihx
> Priority: Major
> Fix For: 2.4.0, 2.3.1
>
>
> If you try to create a topic and the replication factor cannot be satisfied, Kafka will return `INVALID_REPLICATION_FACTOR`. If the topic already exists, we should probably return `TOPIC_ALREADY_EXISTS` instead. You won't see this problem if using TopicCommand because we check existence prior to creating the topic.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)