You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Onur Karaman (JIRA)" <ji...@apache.org> on 2017/05/25 18:29:04 UTC

[jira] [Updated] (KAFKA-5323) AdminUtils.createTopic should check topic existence upfront

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

Onur Karaman updated KAFKA-5323:
--------------------------------
    Status: Patch Available  (was: Open)

> AdminUtils.createTopic should check topic existence upfront
> -----------------------------------------------------------
>
>                 Key: KAFKA-5323
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5323
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Onur Karaman
>            Assignee: Onur Karaman
>
> When a topic exists, AdminUtils.createTopic unnecessarily does N+2 zookeeper reads where N is the number of brokers. Here is the breakdown of the N+2 zookeeper reads:
> # reads the current list of brokers in zookeeper (1 zookeeper read)
> # reads metadata for each broker in zookeeper (N zookeeper reads where N is the number of brokers)
> # checks for topic existence in zookeeper (1 zookeeper read)
> We can reduce the N+2 reads down to 1 by checking topic existence upfront.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)